Re: Long running query causing XID limit breach - Mailing list pgsql-general

From sud
Subject Re: Long running query causing XID limit breach
Date
Msg-id CAD=mzVVqR-mKUFHetsejFWSPQPbLjTVhCmBebJTFX5XmYp+nGg@mail.gmail.com
Whole thread Raw
In response to Re: Long running query causing XID limit breach  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Long running query causing XID limit breach
List pgsql-general

On Thu, May 23, 2024 at 1:45 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:


If a long running query on the standby influences the primary, that means that
you have "hot_standby_feedback" set to "on".  Set it to "off".


Will the setting up of "hot_standby_feedback" value to OFF will cause the reader instance to give incorrect query results or unexpected query failure which will be potential inconsistency between the writer and reader instance, as because those XID's can be removed/cleaned by the writer node even if its being read by the reader instance query. And it can have more replication lag. So I'm wondering , if this setup is advisable one?

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Backup failure Postgres
Next
From: HORDER Philip
Date:
Subject: Re: Restore of a reference database kills the auto analyze processing.