ALTER SUBSCRIPTION REFRESH PUBLICATION has default copy_data = true? - Mailing list pgsql-hackers

From Peter Smith
Subject ALTER SUBSCRIPTION REFRESH PUBLICATION has default copy_data = true?
Date
Msg-id CAHut+PtB-4mzh401Vo2+op-T4xcEPQHEdh2a8biT0Xhm7T8d-g@mail.gmail.com
Whole thread Raw
Responses Re: ALTER SUBSCRIPTION REFRESH PUBLICATION has default copy_data = true?  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Re: ALTER SUBSCRIPTION REFRESH PUBLICATION has default copy_data = true?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
Hi.

The documentation of ALTER SUBSCRIPTION REFRESH PUBLICATION [1] says:

----------

REFRESH PUBLICATION

Fetch missing table information from publisher. This will start
replication of tables that were added to the subscribed-to
publications since the last invocation of REFRESH PUBLICATION or since
CREATE SUBSCRIPTION.

refresh_option specifies additional options for the refresh operation.
The supported options are:

copy_data (boolean)

Specifies whether the existing data in the publications that are being
subscribed to should be copied once the replication starts. The
default is true. (Previously subscribed --tables are not copied.)

----------

But I found that default copy_data = true to be unintuitive.

e.g. When I had previously done the CREATE SUBSCRIPTION using
copy_data = false, then I assumed (wrongly) that the subscription
default would remain as copy_data = false even when doing the REFRESH
PUBLICATION.

Is that a deliberate functionality, or is it a quirk / bug?

------
[1] https://www.postgresql.org/docs/devel/sql-altersubscription.html

Kind Regards,
Peter Smith.
Fujitsu Australia



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Alias collision in `refresh materialized view concurrently`
Next
From: Michael Paquier
Date:
Subject: Re: return correct error code from pgtls_init