| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: DOCS - clarify CREATE SUBSCRIPTION only synchronizes sequences when copy_data=true |
| Date: | 2026-06-25 06:37:30 |
| Message-ID: | CALDaNm1xY_Js5-jppiBzGq2HMqzCHk+LLpupfWp_cFcG=vJXmg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 25 Jun 2026 at 06:22, Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> While reviewing another patch I referred to the information of "29.7.
> Replicating Sequences #" [1] which says:
> "use CREATE SUBSCRIPTION to initially synchronize the published sequences."
>
> AFAIK, that is not entirely correct -- synchronisation of sequences
> happens only when the "copy_data" option is true. Although copy_data
> default is true, the original text was misleading. Anyway, it misled
> me.
>
> PSA a patch to clarify that "copy_data = true" is needed.
Let's include this to avoid confusion.
Few comments:
1) There should be a space after </link>:
+ use <link linkend="sql-createsubscription-params-with-copy-data">
+ <command>CREATE SUBSCRIPTION ... WITH (copy_data = true)</command>
+ </link>to initially synchronize the published sequences.
2) copy_data = true is the default, so it may mislead users into
thinking they must explicitly specify it. How about changing it to:
use CREATE SUBSCRIPTION with the default copy_data = true behavior to
initially synchronize the published sequences.
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-06-25 07:11:29 | Re: Reject unsupported COPY FROM targets before analyzing WHERE clause |
| Previous Message | Kirill Reshke | 2026-06-25 06:33:25 | psql internals queries breaks in presence of user-defined operators |