Re: Make use of unvolatize() in vac_truncate_clog()

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Make use of unvolatize() in vac_truncate_clog()
Date: 2026-02-24 17:19:50
Message-ID: aZ3dthiAZ8nP5Cf7@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 or
removing the volatile qualifier from the variable?

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-02-24 17:27:52 Re: pgsql: libpq: Grease the protocol by default
Previous Message Jacob Champion 2026-02-24 17:18:19 Re: pgsql: libpq: Grease the protocol by default