On 12/25/19 5:34 AM, Dor Ben Dov wrote:
Hi All,
What Is the best recommended / used tool for backup and restore that you
suggest or work with postgres ?
This is the second time around for this question:
https://www.postgresql.org/message-id/AM0PR06MB4817A7035134FD88B2C1D033CC550%40AM0PR06MB4
On 12/25/19 7:46 AM, Andreas Kretschmer wrote:
Am 25.12.19 um 14:34 schrieb Dor Ben Dov:
Hi All,
What Is the best recommended / used tool for backup and restore that you
suggest or work with postgres ?
depends on your needs, most of our customers using barman.
pgbackrest is also popul
Am 25.12.19 um 14:34 schrieb Dor Ben Dov:
Hi All,
What Is the best recommended / used tool for backup and restore that
you suggest or work with postgres ?
depends on your needs, most of our customers using barman.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2n
Am 12.12.19 um 16:12 schrieb Dor Ben Dov:
What is the most common used back and restore solution for postgres ?
most of our customers are using Barman, which is not a surprise since it
is developed by us ;-)
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadra
Hello!
I would recommend to look at pg_probackup:
https://github.com/postgrespro/pg_probackup
On 12/12/19 6:12 PM, Dor Ben Dov wrote:
Hi,
What is the most common used back and restore solution for postgres ?
Which one are you using ?
Regards,
Dor
*This email and the information contained
On 12/12/19 7:12 AM, Dor Ben Dov wrote:
Hi,
What is the most common used back and restore solution for postgres ?
I would say it goes from pg_dump/pg_restore for smaller databases to
some form of replication for larger.
Which one are you using ?
I use pg_dump/pg_restore and have started
On 4/21/19 2:20 PM, Ron wrote:
I see this sort of thing in monitoring systems e.g. environmental
controls all the time. Things get flagged because they wander over set
points intermittently. It is technically an error but unless they stay
over the line it is just another data point.
Errors n
On 4/21/19 3:58 PM, Adrian Klaver wrote:
On 4/21/19 1:42 PM, Ron wrote:
On 4/21/19 1:46 PM, Adrian Klaver wrote:
On 4/21/19 9:35 AM, Daulat Ram wrote:
Hello Team,
We are getting below error while migrating pg_dump from Postgresql 9.6
to Postgresql 11.2 via pg_restore in docker environment.
On 4/21/19 1:42 PM, Ron wrote:
On 4/21/19 1:46 PM, Adrian Klaver wrote:
On 4/21/19 9:35 AM, Daulat Ram wrote:
Hello Team,
We are getting below error while migrating pg_dump from Postgresql
9.6 to Postgresql 11.2 via pg_restore in docker environment.
90d4c9f363c8:~$ pg_restore -d kbcn "/var/
On 4/21/19 1:46 PM, Adrian Klaver wrote:
On 4/21/19 9:35 AM, Daulat Ram wrote:
Hello Team,
We are getting below error while migrating pg_dump from Postgresql 9.6 to
Postgresql 11.2 via pg_restore in docker environment.
90d4c9f363c8:~$ pg_restore -d kbcn "/var/lib/kbcn_backup19"
pg_restore:
Adrian Klaver writes:
> On 4/21/19 9:35 AM, Daulat Ram wrote:
>> pg_restore: [archiver (db)] could not execute query: ERROR: schema
>> "public" already exists
>> Command was: CREATE SCHEMA public;
> Expected as the public schema is there by default. It is an
> informational error, you can ignor
On 4/21/19 9:35 AM, Daulat Ram wrote:
Hello Team,
We are getting below error while migrating pg_dump from Postgresql 9.6
to Postgresql 11.2 via pg_restore in docker environment.
90d4c9f363c8:~$ pg_restore -d kbcn "/var/lib/kbcn_backup19"
pg_restore: [archiver (db)] Error while PROCESSING TOC
12 matches
Mail list logo
