| 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-30 01:29:31 |
| Message-ID: | CAKDb7aGAN5h0tR0CCwOnJYtkRtwuMrYp6MH0sOdd-KWAjKhjSw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi ,
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.
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.
>
> Yours,
> Laurenz Albe
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-05-30 06:07:31 | Re: Queries in replica are failing |
| Previous Message | Laurenz Albe | 2024-05-29 21:17:19 | Re: Queries in replica are failing |