| From: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Include sequences in publications created by pg_createsubscriber |
| Date: | 2026-06-25 05:35:06 |
| Message-ID: | CAE9k0PmZKp_zSNRm7KoLzOjaxnxUjLmA-W02fhg11fqEjB50Vw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Thu, Jun 25, 2026 at 6:29 AM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> 3.
> <para>
> Enable the subscription for each specified database on the target server.
> The subscription starts applying transactions from the replication start
> - point.
> + point. The subscription is configured to include sequences.
> </para>
>
> This implies there was some special subscription "configuration" for
> getting sequences, but it just gets sequences because sequences were
> published. Maybe you don't need to say anything here. Or, maybe reword
> to just say "The subscription will include sequences".
>
What if the subscription uses an existing publication that doesn't
include sequences? In that case, would it be correct to say that the
subscription will include sequences?
--
With Regards,
Ashutosh Sharma.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | cca5507 | 2026-06-25 05:53:39 | Re: Handle concurrent drop when doing whole database vacuum |
| Previous Message | Amit Langote | 2026-06-25 05:25:41 | Re: In core use of RegisterXactCallback() and RegisterSubXactCallback() |