Re: Fix uninitialized xl_running_xacts padding

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Alexander Kuzmenkov <akuzmenkov(at)tigerdata(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix uninitialized xl_running_xacts padding
Date: 2026-03-22 06:50:06
Message-ID: ab-RHkucjKUFXgY3@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 18, 2026 at 02:18:45PM +0200, Heikki Linnakangas wrote:
> I think if you use "BEGIN; INSERT ...; ROLLBACK;" to generate the dead
> tuples instead of DELETE, it will not be sensitive to concurrent snapshots
> like that.

Nice trick, this makes the test stable. I have reused it and applied
this part to take care of the coverage hole.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2026-03-22 08:50:31 Re: Non-text mode for pg_dumpall
Previous Message John Naylor 2026-03-22 05:26:24 Re: vectorized CRC on ARM64