| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | John Naylor <johncnaylorls(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: get rid of RM_HEAP2_ID |
| Date: | 2025-10-15 14:39:38 |
| Message-ID: | 633f0bcf-f313-466b-aa09-c6f62056178f@iki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15/10/2025 07:51, John Naylor wrote:
> On Tue, Oct 14, 2025 at 7:20 PM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> This patch consumes one of the padding bytes. That's not entirely free,
>> as there is an opportunity cost: we could squeeze out the padding bytes
>> and save 2 bytes on every WAL record instead.
>
> I must be misunderstanding, because I'm not sure how that would work
> with the alignment requirement of later parts.
We could store xl_crc unaligned. IIRC all the structs that follow that
are already stored unaligned.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Srinath Reddy Sadipiralla | 2025-10-15 14:52:34 | Re: Making pg_rewind faster |
| Previous Message | Heikki Linnakangas | 2025-10-15 14:35:58 | Re: get rid of RM_HEAP2_ID |