| From: | Abhishek Prakash <abhishek(dot)prakash08(at)infosys(dot)com> |
|---|---|
| To: | "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> |
| Subject: | ***Conflict with recovery error*** |
| Date: | 2023-01-20 08:56:49 |
| Message-ID: | SI2PR02MB5490F6959EF4B92A9CC41C2681C59@SI2PR02MB5490.apcprd02.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Hi Team,
Hope you guys are doing good.
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(at)ubprdb01:[17707]:ERROR: canceling statement due to conflict with recovery
2023-01-13 07:20:12 UTC:10.64.103.75(61096):ubpreplica(at)ubprdb01:[17707]:DETAIL: User query might have needed to see row versions that must be removed.
Thanks & Regards,
Abhishek P
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-01-20 09:55:48 | Re: ***Conflict with recovery error*** |
| Previous Message | David G. Johnston | 2023-01-19 22:51:04 | Re: Documentation discrepancy UNIQUE NULLS NOT DISTINCT |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Pyhalov | 2023-01-20 09:00:04 | Re: Add semi-join pushdown to postgres_fdw |
| Previous Message | shveta malik | 2023-01-20 08:53:45 | Re: Time delayed LR (WAS Re: logical replication restrictions) |