SIReadLock vs hot_standby_feedback

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: SIReadLock vs hot_standby_feedback
Date: 2022-08-18 20:28:25
Message-ID: FDFFA6D8-9F21-480E-A5B4-43A727DEBEB2@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I am reasonably sure the answer to this is "no", but can the oldest xmin that hot_standby_feedback sends to the primary also delay SIReadLocks cleanup? Going through the code, it looks like they're independent, but this isn't a part of the system I know particularly well.

Browse pgsql-general by date

  From Date Subject
Next Message milist ujang 2022-08-18 22:55:03 Re: ERROR: catalog is missing 3 attribute(s) for relid 150243
Previous Message W.P. 2022-08-18 19:54:08 Re: Is it possible to keep indexes on different disk location?