From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_verify_checksums and -fno-strict-aliasing |
Date: | 2018-09-01 19:32:10 |
Message-ID: | 12600.1535830330@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Petr Jelinek | 2018-09-01 19:40:52 | Re: Some pgq table rewrite incompatibility with logical decoding? |
Previous Message | Tom Lane | 2018-09-01 19:04:21 | Re: [PATCH] Fix docs to JOHAB encoding on server side |