Re: Clear padding in PgStat_HashKey keys - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: Clear padding in PgStat_HashKey keys
Date
Msg-id Zyic6YpRG863J6aN@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Clear padding in PgStat_HashKey keys  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers
Hi,

On Mon, Nov 04, 2024 at 06:49:04PM +0900, Michael Paquier wrote:
> On Mon, Nov 04, 2024 at 08:52:04AM +0000, Bertrand Drouvot wrote:
> > Yeah, but not only the relfilenode ones. All kinds were affected as random data
> > was in the padding bytes for all of them.
> 
> A quick test where I add some padding junk in PgStat_HashKey proves
> that you are right.

Thanks for the testing!

> I'm wondering if we should backpatch that,
> actually, down to where it has been introduced.  We are unlikely going
> to change this structure,

Yeah.

> but if we do for the sake of a bug fix,
> which is always a possibility as ABI does not matter much for this
> internal structure, that's potentially trouble waiting ahead.

That's right.

> Thoughts?

hm, yeah I think that it could fall into the "low-risk fixes" category [0] and
that we can opt for backpatch.

[0]: https://www.postgresql.org/support/versioning/

Regards,

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



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: per backend I/O statistics
Next
From: Matthias van de Meent
Date:
Subject: Re: protocol-level wait-for-LSN