Re: Allow logical replication to copy tables in binary format - Mailing list pgsql-hackers

On Fri, Mar 17, 2023 at 12:20 AM Melih Mutlu <m.melihmutlu@gmail.com> wrote:
>
> Hi,
>
> Please see the attached v16.
>
> Peter Smith <smithpb2250@gmail.com>, 16 Mar 2023 Per, 03:03 tarihinde şunu yazdı:
>>
>> Here are some review comments for v15-0001
>
>
> I applied your comments in the updated patch.

Thanks.

I checked patchv16-0001 and have only one minor comment.

======
doc/src/sgml/logical-replication.sgml

1.
diff --git a/doc/src/sgml/logical-replication.sgml
b/doc/src/sgml/logical-replication.sgml
index 6b0e300adc..bad25e54cd 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -251,7 +251,10 @@
    column of type <type>bigint</type>.  The target table can also have
    additional columns not provided by the published table.  Any such columns
    will be filled with the default value as specified in the definition of the
-   target table.
+   target table. However, logical replication in <literal>binary</literal>
+   format is more restrictive. See the <literal>binary</literal> option of
+   <link linkend="sql-createsubscription"><command>CREATE
SUBSCRIPTION</command></link>
+   for details.
   </para>

IMO the sentence "However, logical replication in binary format is
more restrictive." should just be plain text.

There should not be the <literal>binary</literal> markup in that 1st sentence.

------
Kind Regards,
Peter Smith.
Fujitsu Australia