| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Lucas <root(at)sud0(dot)nz> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 9.2 high replication lag |
| Date: | 2021-07-14 03:14:11 |
| Message-ID: | CAKFQuwayvL=PLFu=UxV5pBakJfiwLyqp33_cSc+VNb2UOS_q1w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jul 13, 2021 at 8:01 PM Lucas <root(at)sud0(dot)nz> wrote:
> According to the documentation, max_standby_streaming_delay is a configuration
> parameter <https://pgpedia.info/g/guc.html> determining how long a
> standby server should wait before canceling queries that conflict with
> pending WAL entries received via streaming replication.
>
> My question then is: Which queries, if the slave can only receive SELECTs?
>
The select queries...
Follow the link in the docs for max_stanbdy_steaming_delay to:
https://www.postgresql.org/docs/current/hot-standby.html#HOT-STANDBY-CONFLICT
for the details.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2021-07-14 05:30:51 | Re: PostgreSQL 9.2 high replication lag |
| Previous Message | Lucas | 2021-07-14 03:01:10 | Re: PostgreSQL 9.2 high replication lag |