Re: Fix ALTER SUBSCRIPTION ... SET PUBLICATION documentation - Mailing list pgsql-hackers

From japin
Subject Re: Fix ALTER SUBSCRIPTION ... SET PUBLICATION documentation
Date
Msg-id MEYP282MB1669895C05325DCAA5E352D8B6BB0@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Fix ALTER SUBSCRIPTION ... SET PUBLICATION documentation  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Wed, 27 Jan 2021 at 19:47, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote:
> On Wed, Jan 27, 2021 at 4:57 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>>
>> On Tue, Jan 26, 2021 at 4:56 PM japin <japinli@hotmail.com> wrote:
>> >
>> >
>> > Hi,
>> >
>> > When I read the documentation of ALTER SUBSCRIPTION ... SET PUBLICATION ... WITH (...),
>> > it says "set_publication_option" only support "refresh" in documentation [1].
>> > However, we can also supply the "copy_data" option, and the code is:
>> >
>>
>> I think there is a reference to the 'copy_data' option as well. There
>> is a sentence saying: "Additionally, refresh options as described
>> under REFRESH PUBLICATION may be specified." and then if you Refresh
>> option, there we do mention about 'copy_data', isn't that sufficient?
>
> Right. It looks like the copy_option is indirectly mentioned with the
> statement "Additionally, refresh options as described under REFRESH
> PUBLICATION may be specified." under "set_publication_option". IMHO,
> we can keep it that way.
>

My bad. It may be sufficient. Sorry for noise.

-- 
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: simplifying foreign key/RI checks
Next
From: vignesh C
Date:
Subject: Re: Printing backtrace of postgres processes