PG12: Any drawback of increasing wal_keep_segments

2022-03-24 Thread Shukla, Pranjal
Team, Are there any disadvantages of increasing the “wal_keep_segments” to a higher number say, 500? Will it have any impact on performance of streaming replication, on primary or secondary servers? Thanks & Regards Pranjal Shukla

Re: Query on WAL Optimization and Streaming Replication

2022-03-17 Thread Shukla, Pranjal
Ok, Then what will increase the size of the WAL? Sent from my iPhone > On 17-Mar-2022, at 8:08 PM, Laurenz Albe wrote: > On Thu, 2022-03-17 at 14:05 +, Shukla, Pranjal wrote: >> From the configuration we have, does it mean that the primary will retain 32 >> WAL's &

Re: Query on WAL Optimization and Streaming Replication

2022-03-17 Thread Shukla, Pranjal
_buffers = 16MB min_wal_size = 1GB max_wal_size = 2GB Thanks & Regards Pranjal Shukla On 3/17/22, 6:50 PM, "Laurenz Albe" wrote: On Thu, 2022-03-17 at 12:36 +, Shukla, Pranjal wrote: > uring upgrades of our application, we generally shutdown all Secondary servers >

Query on WAL Optimization and Streaming Replication

2022-03-17 Thread Shukla, Pranjal
During upgrades of our application, we generally shutdown all Secondary servers which are getting stream replicated from Primary Servers. This is to maintain a copy of database on other servers should we wish to revert (of course we take DB Backups too before starting the activity). After the ap

Re: Restoring using PG_DUMP in PG12 results in

2022-03-15 Thread Shukla, Pranjal
njal Shukla On 3/14/22, 8:25 PM, "Adrian Klaver" wrote: On 3/14/22 06:39, Shukla, Pranjal wrote: > Hello, > > We tried importing into an empty database in PG 12 from the dump that > was created in PG 10. Import was successful but we got an message t

Restoring using PG_DUMP in PG12 results in

2022-03-14 Thread Shukla, Pranjal
Hello, We tried importing into an empty database in PG 12 from the dump that was created in PG 10. Import was successful but we got an message that an error was ignored. We agin imported with -e option and the following message was printed: pg_restore: while PROCESSING TOC: pg_restore: from TO