public inbox for [email protected]  

help / color / mirror / Atom feed

From: Abhishek Prakash <[email protected]>
To: Laurenz Albe <[email protected]>
To: [email protected] <[email protected]>
To: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Cc: RaviTeja Pippalla <[email protected]>
Subject: RE: ***Conflict with recovery error***
Date: Fri, 20 Jan 2023 09:59:12 +0000
Message-ID: <SI2PR02MB5490CF8B0D514EB671AF3ACB81C59@SI2PR02MB5490.apcprd02.prod.outlook.com> (raw)
In-Reply-To: <[email protected]>
References: <SI2PR02MB5490F6959EF4B92A9CC41C2681C59@SI2PR02MB5490.apcprd02.prod.outlook.com>
	<[email protected]>

Hi Laurenz,

Thanks for your reply.
We had set max_standby_streaming_delay = -1, but faced storage issues nearly 3.5 TB of storage was consumed. 

Regards,
Abhishek P

-----Original Message-----
From: Laurenz Albe <[email protected]> 
Sent: Friday, January 20, 2023 3:26 PM
To: Abhishek Prakash <[email protected]>; [email protected]; [email protected]; [email protected]
Subject: Re: ***Conflict with recovery error***

[**EXTERNAL EMAIL**]

On Fri, 2023-01-20 at 08:56 +0000, 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 is nearly 6 TB which runs as AWS Postgres RDS.
>
> Even the below error occurs on tables where vacuum is disabled and no 
> DML operations are permitted. Will there be any chances to see row 
> versions being changed even if vacuum is disabled.
> Please advise.
>
> 2023-01-13 07:20:12 
> UTC:10.64.103.75(61096):ubpreplica@ubprdb01:[17707]:ERROR:  canceling 
> statement due to conflict with recovery
> 2023-01-13 07:20:12 UTC:10.64.103.75(61096):ubpreplica@ubprdb01:[17707]:DETAIL:  User query might have needed to see row versions that must be removed.

It could be HOT chain pruning or an anti-wraparound autovacuum (which runs even if autovacuum is disabled).
Disabling autovacuum is not a smart idea to begin with.

Your best bet is to set "max_standby_streaming_delay = -1".

More reading:
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cybertec-postgresql.com%2Fen%2...

Yours,
Laurenz Albe

view thread (3+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: RE: ***Conflict with recovery error***
  In-Reply-To: <SI2PR02MB5490CF8B0D514EB671AF3ACB81C59@SI2PR02MB5490.apcprd02.prod.outlook.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox