From: | ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Siraj G <tosiraj(dot)g(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Queries in replica are failing |
Date: | 2024-05-29 17:04:46 |
Message-ID: | CAKDb7aFyV_079RHWga+tjb_PJ7JT31JPRGHRx6P7Bi+1wMgNiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I received this error when i set max_standby_streaming_delay to -1
and max_standby_archive_delay
to 30 seconds.
The following processes were terminated on your read replica because they
were interfering with the replay of transaction logs: [18218].
I was also receiving an error when i set *hot_standby_feedback.*
*Kindly suggest.*
On Thu, May 16, 2024 at 8:04 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Thu, 2024-05-16 at 17:31 +0530, Siraj G wrote:
> > Queries in replica instance are failing with the error
> "cancelling statement due
> > to conflict with recovery". I was checking two parameters
> (max_standby_archive_delay
> > and max_standby_streaming_delay) which may allow the queries to run
> within the
> > time defined in those.
> >
> > Is it recommended to set those? Is there any other suggestion to tackle
> this?
>
> The only safe way to avoid this error is to set
> "max_standby_streaming_delay" to -1.
>
> See
> https://www.cybertec-postgresql.com/en/streaming-replication-conflicts-in-postgresql/
>
> Yours,
> Laurenz Albe
>
>
>
--
Have a Good day !!!
Regards
Rohit Sachdeva
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-05-29 21:17:19 | Re: Queries in replica are failing |
Previous Message | Laurenz Albe | 2024-05-29 15:05:54 | Re: Questions on recovery situations (not urgent) |