Re: Binary support for pgoutput plugin - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: Binary support for pgoutput plugin
Date
Msg-id CADK3HHLmbnRSCfE0PoBjNdgZiep+o-frxBUFfywPcRb=TgFs9g@mail.gmail.com
Whole thread Raw
In response to Re: Binary support for pgoutput plugin  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Binary support for pgoutput plugin  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers


On Sat, 11 Jul 2020 at 10:20, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Petr Jelinek <petr@2ndquadrant.com> writes:
> On 11/07/2020 14:14, Dave Cramer wrote:
>> So is there any point in having them as options then ?

> I am guessing this is copied from pglogical, right? We have them there
> because it can optionally send data in the on-disk format (not the
> network binary format) and there this matters, but for network binary
> format they do not matter as Tom says.

Ah, I wondered why that was there at all.  Yes, you should just delete
all that logic --- it's irrelevant as long as we use the send/recv
functions.

                        regards, tom lane


Ok,

removed all the unnecessary options. 
Added the test case that Daniel had created.
Added a note to the docs.

Note WAL_DEBUG is removed in patch 3. I could rebase that into patch 1 if required.

Thanks,

Dave
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Editing errors in the comments of tableam.h and heapam.c
Next
From: Stephen Frost
Date:
Subject: Re: Default setting for enable_hashagg_disk