Re: Queries in replica are failing

okay..

So What will be the work around for this.

On Thu, May 30, 2024 at 11:37 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> On Thu, 2024-05-30 at 06:59 +0530, ROHIT SACHDEVA wrote:
> > On Thu, 30 May, 2024, 2:47 am Laurenz Albe, <laurenz(dot)albe(at)cybertec(dot)at>
> wrote:
> > > On Wed, 2024-05-29 at 22:34 +0530, ROHIT SACHDEVA wrote:
> > > > 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].
> > >
> > > Ah, then you are recovering from an archive.
> > >
> > > In that case, set "max_standby_archive_delay" to -1 as well.
> >
> > If I set both to -1 storage space is increasing rapidly.
> >
> > Any way out as they are okay with 1 day delay but queries should run
> smoothly.
> >
> > Can I pause or schedule the replication process replication at 12 am in
> Postgres RDS.
>
> Sure, WAL will pile up on the standby if it cannot be replayed right away.
>
> You could stop replication, but then WAL would pile up on the primary
> server.
>
> You have to keep the information somewhere.
>
> Yours,
> Laurenz Albe
>

--
Have a Good day !!!

Regards
Rohit Sachdeva