public inbox for [email protected]
help / color / mirror / Atom feedFrom: Torsten Förtsch <[email protected]>
To: Jethish Jethish <[email protected]>
Cc: [email protected]
Subject: Re: Backup failure Postgres
Date: Thu, 23 May 2024 12:23:00 +0200
Message-ID: <CAKkG4_=V2UN62_CjRohbpZ_uxP56ai465ohNp1bt-+r41wCxig@mail.gmail.com> (raw)
In-Reply-To: <CAKeSjMhHx1cMSTPTP7szhyV5Mt21YuA98Q+hS9+W2nrj0U9N3Q@mail.gmail.com>
References: <CAKeSjMhHx1cMSTPTP7szhyV5Mt21YuA98Q+hS9+W2nrj0U9N3Q@mail.gmail.com>
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 <[email protected]>
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;
>
view thread (2+ 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]
Subject: Re: Backup failure Postgres
In-Reply-To: <CAKkG4_=V2UN62_CjRohbpZ_uxP56ai465ohNp1bt-+r41wCxig@mail.gmail.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