Re: Question about InvalidatePossiblyObsoleteSlot()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "suyu(dot)cmj" <mengjuan(dot)cmj(at)alibaba-inc(dot)com>, "bharath(dot)rupireddyforpostgres" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Question about InvalidatePossiblyObsoleteSlot()
Date: 2025-10-30 05:55:33
Message-ID: aQL91fWz8I9Qz4dB@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 30, 2025 at 04:18:26AM +0000, Bertrand Drouvot wrote:
> The tests are also stabilized on 17 thanks to 17a165d60f73 and on 16 thanks
> to 86392e8827d8, so I think that we should be fine on those branches too.

Applied down to v16, including the comment when the LWLock is
released for consistency across all the branches. The buildfarm will
now tell a bit more.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-10-30 06:04:05 Re: Skipping schema changes in publication
Previous Message Chao Li 2025-10-30 05:43:34 Re: tuple radix sort