Re: Fix race condition in InvalidatePossiblyObsoleteSlot()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, exclusion(at)gmail(dot)com
Subject: Re: Fix race condition in InvalidatePossiblyObsoleteSlot()
Date: 2024-03-06 11:21:14
Message-ID: ZehRqmcB2kt6FlzH@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 06, 2024 at 09:17:58AM +0000, Bertrand Drouvot wrote:
> Right, somehow out of context here.

We're not yet in the green yet, one of my animals has complained:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hachi&dt=2024-03-06%2010%3A10%3A03

This is telling us that the xmin horizon is unchanged, and the test
cannot move on with the injection point wake up that would trigger the
following logs:
2024-03-06 20:12:59.039 JST [21143] LOG: invalidating obsolete replication slot "injection_activeslot"
2024-03-06 20:12:59.039 JST [21143] DETAIL: The slot conflicted with xid horizon 770.

Not sure what to think about that yet.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2024-03-06 11:24:06 Re: speed up a logical replica setup
Previous Message John Naylor 2024-03-06 11:20:35 Re: [PoC] Improve dead tuple storage for lazy vacuum