From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndQuadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Missing FIN_CRC32 calls in logical replication code |
Date: | 2014-11-13 22:04:52 |
Message-ID: | 54652B04.6080100@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/11/2014 06:55 PM, Andres Freund wrote:
> On 2014-11-03 21:58:51 +0200, Heikki Linnakangas wrote:
>> PS. I find the name "ReplicationSlotOnDiskDynamicSize" confusing, as it is
>> in fact a fixed size struct. I gather it's expected that the size of that
>> part might change across versions, but by that definition nothing is
>> constant.
>
> Well, the idea is that the 'constant' part is version independent. The
> part following afterwards (dynamic) can differ based on the 'version'
> struct member. The reason is that that allows files from older releases
> to be read after a pg_upgrade.
>
> If you have suggestions for better names.
(It's a bit late, I know, but...)
I would actually suggest using the 'magic' field as the version
identifier. Increment it by one on every version change. It would be
handy to have the version ID as the first field in the file.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-11-13 22:18:18 | Re: Inconsistencies in documentation of row-level locking |
Previous Message | Jeff Davis | 2014-11-13 21:57:01 | Re: group locking: incomplete patch, just for discussion |