Re: Backup failure Postgres
От | Jethish Jethish |
---|---|
Тема | Re: Backup failure Postgres |
Дата | |
Msg-id | CAKeSjMh3YKDkcDORDL8cE4DbwaAuWrRz_aoS1GoS-XX=Ki5KvQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Backup failure Postgres (Torsten Förtsch <tfoertsch123@gmail.com>) |
Ответы |
Re: Backup failure Postgres
Re: Backup failure Postgres |
Список | pgsql-general |
Hi Torsten,
I have tried by increasing the max_standby_streaming_delay but I'm facing lag issues on the replica server.
When i increase the max_standby_streaming_delay even if a query runs for 2 minutes I'm facing lag issues for 2 minutes.
Please suggest here.
Data size is 3TB
On Thu, May 23, 2024, 3:53 PM Torsten Förtsch <tfoertsch123@gmail.com> wrote:
As the error message says, your query was aborted due to it conflicting with recovery. There are many ways to deal with that. You could enable hot_standby_feedback on the replica. You could disconnect the replica from the master for the time the COPY takes (reset primary_conninfo). You could increase max_standby_streaming_delay. Perhaps you could also wrap the COPY operation in pg_wal_replay_pause() / pg_wal_replay_resume().On Thu, May 23, 2024 at 11:59 AM Jethish Jethish <jethish777@gmail.com> wrote:I'm frequently facing the below error while performing backup. Someone please tell how solve this issues.Failed : pg_dump: error: Dumping the contents of table "botsession" failed: PQgetResult() failed. pg_dump: error: Error message from server: ERROR: canceling statement due to conflict with recovery DETAIL: User query might have needed to see row versions that must be removed. pg_dump: error: The command was: COPY public.botsession (id, userid, data, iscompressed) TO stdout;
В списке pgsql-general по дате отправления: