Re: Corrected documentation of data type for the logical replication message formats.

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: Euler Taveira <euler(at)eulerto(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Corrected documentation of data type for the logical replication message formats.
Date: 2021-07-23 16:01:09
Message-ID: CALDaNm28D3YSo=NNhoZinMv0eK_b2vPTVTAdmieKphpPhF6erQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 23, 2021 at 3:23 AM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> I think the patch maybe is not quite correct for all the flags.
>
> For example,
>
> @@ -7607,44 +7615,44 @@ are available since protocol version 3.
> <varlistentry>
> <term>Int8</term>
> <listitem><para>
> - Flags; currently unused (must be 0).
> + Flags (uint8); currently unused.
> </para></listitem>
> </varlistentry>
>
> AFAIK, even though the flags are "unused", the code still insists that
> most (or all? Please check the code) of these flag values MUST be 0,
> so I think that this zero value requirement ought to be indicated in
> the docs using the "Int8(0)" convention [1]. For example,
>
> BEFORE
> Int8
> Flags (uint8); currently unused.
>
> AFTER
> Int8(0)
> Flags (uint8); currently unused.

Thanks for the comments. Attached v6 patch has the changes for the same.

Regards,
Vignesh

Attachment Content-Type Size
v6-0001-Included-the-actual-datatype-used-in-logical-repl.patch text/x-patch 16.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-07-23 16:08:51 Re: Slightly improve initdb --sync-only option's help message
Previous Message Tom Lane 2021-07-23 15:50:09 Re: WIP: Relaxing the constraints on numeric scale