Re: Make use of unvolatize() in vac_truncate_clog() - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: Make use of unvolatize() in vac_truncate_clog()
Date
Msg-id aZ3q6omjSsQ6NoRV@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Make use of unvolatize() in vac_truncate_clog()  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Make use of unvolatize() in vac_truncate_clog()
List pgsql-hackers
Hi,

On Tue, Feb 24, 2026 at 11:19:50AM -0600, Nathan Bossart wrote:
> On Tue, Feb 24, 2026 at 05:08:09PM +0000, Bertrand Drouvot wrote:
> > This patch makes use of unvolatize() in vac_truncate_clog().
> > 
> > Note that it does not remove the warning but moves it to c.h (where unvolatize()
> > is defined) but that's consistent with what 481018f2804 did too.
> 
> Why is this preferable to marking the function parameter as volatile

I think that that would sound misleading for the other callers that don't really
need the volatile qualification.

> or  removing the volatile qualifier from the variable?

That looks mandatory according to 2d2e40e3bef.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: index prefetching
Next
From: "Joel Jacobson"
Date:
Subject: [BUG?] estimate_hash_bucket_stats uses wrong ndistinct for avgfreq