Re: pg_verify_checksums and -fno-strict-aliasing - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_verify_checksums and -fno-strict-aliasing
Date
Msg-id 12600.1535830330@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_verify_checksums and -fno-strict-aliasing  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_verify_checksums and -fno-strict-aliasing  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Fri, Aug 31, 2018 at 07:59:58PM -0400, Tom Lane wrote:
>> The others you mention could be changed, probably, but I didn't
>> bother as they didn't seem performance-critical.

> It is not really critical indeed.  There is an argument to change them
> so as other folks get used to it though.

Fair enough.  I renamed the types as suggested, changed a few more
places for consistency's sake, and pushed.

There still remain some places where palloc(BLCKSZ) or equivalent is used,
but there's no matching pfree.  In a lot of them the buffer is returned
to the caller so there's no choice.  It's likely that some are just
leaking the storage transiently and we could convert them to using a
PGAlignedBlock local variable, but I didn't bother trying to do the
analysis.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Fix docs to JOHAB encoding on server side
Next
From: Petr Jelinek
Date:
Subject: Re: Some pgq table rewrite incompatibility with logical decoding?