From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | kdg(dot)dev(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Ambiguous description on new columns |
Date: | 2024-05-22 03:05:37 |
Message-ID: | CAKFQuwbUuQu0_DbGBUyQ4DqYhR35Vm2_xsB1SY1nZHm5KcXhig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Tue, May 21, 2024 at 3:40 AM PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page:
> https://www.postgresql.org/docs/16/logical-replication-col-lists.html
> Description:
>
> The documentation on this page mentions:
>
> "If no column list is specified, any columns added later are automatically
> replicated."
>
> It feels ambiguous what this could mean. Does it mean:
>
> 1/ That if you alter the table on the publisher and add a new column, it
> will be replicated
>
Yes, this is the only thing in scope you can "add columns to later".
> 2/ If you add a column list later and add a column to it, it will be
> replicated
>
I feel like we failed somewhere if the reader believes that it is possible
to alter a publication in this way.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2024-05-22 03:21:32 | Re: Ambiguous description on new columns |
Previous Message | Peter Smith | 2024-05-22 02:47:39 | Re: Ambiguous description on new columns |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2024-05-22 03:21:32 | Re: Ambiguous description on new columns |
Previous Message | David Rowley | 2024-05-22 03:05:20 | Re: Path to unreverting "Allow planner to use Merge Append to efficiently implement UNION" |