Pushed. On Tue, Aug 25, 2026 at 5:32 AM Bertrand Drouvot <[email protected]> wrote: > On Mon, Aug 24, 2026 at 07:07:07PM -0400, Peter Geoghegan wrote: > > On Wed, Jul 29, 2026 at 5:36 AM Bertrand Drouvot > > <[email protected]> wrote: > > > > 1/ In ExportSnapshot(), do not include recovery subxip entries and > > > > committed > > > > child XIDs at or above xmax when counting and serializing them, so > > > > unnecessary > > > > entries do not consume the limited recovery subxip capacity. > > > > That is a valid issue, but I wonder if it's worth including in a > > back-patchable fix. Is the special case worth the added risk? > > Yeah, probably not. What about adding an XXX here:
In the committed version, we raise a specific ERROR when this happens. I think it's unlikely that any user will ever see this ERROR, but it's better to have it and not need it. Thanks -- Peter Geoghegan
