| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Abhishek Prakash <abhishek(dot)prakash08(at)infosys(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "usergroups(at)postgresql(dot)org" <usergroups(at)postgresql(dot)org> |
| Cc: | RaviTeja Pippalla <raviteja(dot)pippalla(at)edgeverve(dot)com> |
| Subject: | Re: ***Conflict with recovery error*** |
| Date: | 2023-01-20 10:08:49 |
| Message-ID: | 13a32ee99ed73642acd9d0c574c3acf03d355311.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Fri, 2023-01-20 at 09:59 +0000, 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 disk storage.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitrios Apostolou | 2023-01-20 20:01:22 | Re: Why is a hash join preferred when it does not fit in work_mem |
| Previous Message | Abhishek Prakash | 2023-01-20 09:59:12 | RE: ***Conflict with recovery error*** |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Katsuragi Yuta | 2023-01-20 10:41:41 | Re: [Proposal] Add foreign-server health checks infrastructure |
| Previous Message | Thomas Munro | 2023-01-20 10:02:46 | Re: DSA failed to allocate memory |