From: | vignesh C <vignesh21(at)gmail(dot)com> |
---|---|
To: | "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH]Comment improvement in publication.sql |
Date: | 2021-08-08 09:34:09 |
Message-ID: | CALDaNm3N0QzMDSW6BzhupBDhsgiNVM2bLFx2=kMjTaXxgUvhgQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 6, 2021 at 3:33 PM tanghy(dot)fnst(at)fujitsu(dot)com
<tanghy(dot)fnst(at)fujitsu(dot)com> wrote:
>
> Hi
>
> I saw some inaccurate comments for AlterPublicationStmt structure when
> reviewing patches related to publication[1].
>
> The variable tables are used for 'ALTER PUBLICATION ... ADD/DROP/SET TABLE',
> but the comments only say 'ADD/DROP'. How about add 'SET' to the comments?
>
> typedef struct AlterPublicationStmt
> {
> NodeTag type;
> char *pubname; /* Name of the publication */
>
> /* parameters used for ALTER PUBLICATION ... WITH */
> List *options; /* List of DefElem nodes */
>
> /* parameters used for ALTER PUBLICATION ... ADD/DROP TABLE */
> List *tables; /* List of tables to add/drop */
> bool for_all_tables; /* Special publication for all tables in db */
> DefElemAction tableAction; /* What action to perform with the tables */
> } AlterPublicationStmt;
>
> It's also a comment improvement, so I add this change to this patch.
Thanks for the updated patch, your changes look good to me. You might
want to include the commit message in the patch, that will be useful.
Regards,
Vignesh
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-08-08 10:11:12 | Re: Use generation context to speed up tuplesorts |
Previous Message | vignesh C | 2021-08-08 09:22:22 | Re: Added schema level support for publication. |