Re: ***Conflict with recovery error***

2023-01-20 Thread Laurenz Albe
On Fri, 2023-01-20 at 09:59 +, Abhishek Prakash wrote: > We had set max_standby_streaming_delay = -1, but faced storage issues > nearly 3.5 TB of storage was consumed. Then either don't run queries that take that long or run fewer data modifications on the primary. Or invest in a few more TB

RE: ***Conflict with recovery error***

2023-01-20 Thread Abhishek Prakash
...@lists.postgresql.org; pgsql-hackers@lists.postgresql.org; usergro...@postgresql.org Subject: Re: ***Conflict with recovery error*** [**EXTERNAL EMAIL**] On Fri, 2023-01-20 at 08:56 +, Abhishek Prakash wrote: > We are facing below issue with read replica we did work arounds by > s

Re: ***Conflict with recovery error***

2023-01-20 Thread Laurenz Albe
On Fri, 2023-01-20 at 08:56 +, Abhishek Prakash wrote: > We are facing below issue with read replica we did work arounds by setting > hot_standby_feedback, max_standby_streaming_delay and > max_standby_archive_delay, > which indeed caused adverse effects on primary DB and storage. As our DB