MIME-Version: 1.0
References: <CAKeSjMhHx1cMSTPTP7szhyV5Mt21YuA98Q+hS9+W2nrj0U9N3Q@mail.gmail.com>
In-Reply-To: <CAKeSjMhHx1cMSTPTP7szhyV5Mt21YuA98Q+hS9+W2nrj0U9N3Q@mail.gmail.com>
From: =?UTF-8?Q?Torsten_F=C3=B6rtsch?= <tfoertsch123@gmail.com>
Date: Thu, 23 May 2024 12:23:00 +0200
Message-ID: <CAKkG4_=V2UN62_CjRohbpZ_uxP56ai465ohNp1bt-+r41wCxig@mail.gmail.com>
Subject: Re: Backup failure Postgres
To: Jethish Jethish <jethish777@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000002b478706191c7079"
Archived-At: <https://www.postgresql.org/message-id/CAKkG4_%3DV2UN62_CjRohbpZ_uxP56ai465ohNp1bt-%2Br41wCxig%40mail.gmail.com>
Precedence: bulk

--0000000000002b478706191c7079
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM 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 que=
ry
> might have needed to see row versions that must be removed. pg_dump: erro=
r:
> The command was: COPY public.botsession (id, userid, data, iscompressed) =
TO
> stdout;
>

--0000000000002b478706191c7079
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As the error message says, your query was aborted due to i=
t conflicting with recovery. There are many ways to deal with that. You cou=
ld enable hot_standby_feedback on the replica. You could disconnect the rep=
lica 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().</div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Th=
u, May 23, 2024 at 11:59=E2=80=AFAM Jethish Jethish &lt;<a href=3D"mailto:j=
ethish777@gmail.com">jethish777@gmail.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">I&#39;m frequent=
ly facing the below error while performing backup. Someone please tell how =
solve this issues.<div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><p style=3D"margin-top:0px;margin-bottom:0px">Failed : pg_=
dump: error: Dumping the contents of table &quot;botsession&quot; failed: P=
QgetResult() failed. pg_dump: error: Error message from server: ERROR: canc=
eling statement due to conflict with recovery DETAIL: User query might have=
 needed to see row versions that must be removed. pg_dump: error: The comma=
nd was: COPY public.botsession (id, userid, data, iscompressed) TO stdout;<=
/p></div></div>
</blockquote></div>

--0000000000002b478706191c7079--