Re: Skipping schema changes in publication

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, YeXiu <1518981153(at)qq(dot)com>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Skipping schema changes in publication
Date: 2025-11-17 07:51:57
Message-ID: CAHut+PuHn-hohA4OdEJz+Zfukfr41TvMTeTH7NwJ=wg1+94uNA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Shlok,

A comment about patch v27-0003

======
doc/src/sgml/logical-replication.sgml

All references to tables "t1" and "t2" should use the <structname> tag
in the SGML. The current patch has broken this in multiple places:

e.g.
- Create a table <structname>t1</structname> to be used in the
following example.
+ Create tables <literal>t1</literal> and <literal>t2</literal> to be used in
+ the following example.

~~

e.g.
- table <structname>t1</structname> to reduce the number of columns
that will be
- replicated. Notice that the order of column names in the column list does
- not matter.
+ table <literal>t1</literal>, and another column list is defined for table
+ <literal>t2</literal> using the <literal>EXCEPT</literal> clause to reduce
+ the number of columns that will be replicated. Note that the
order of column
+ names in the column lists does not matter.

~~

e.g.
- On the subscriber node, create a table
<structname>t1</structname> which now
- only needs a subset of the columns that were on the publisher table
- <structname>t1</structname>, and also create the subscription
+ On the subscriber node, create tables <literal>t1</literal> and
+ <literal>t2</literal> which now only needs a subset of the columns that
+ were on the publisher tables <literal>t1</literal> and
+ <literal>t2</literal>, and also create the subscription

~~

e.g.
- On the publisher node, insert some rows to table
<structname>t1</structname>.
+ On the publisher node, insert some rows to tables <literal>t1</literal>
+ and <literal>t2</literal>

======
Kind Regards,
Peter Smith.
Fujitsu Australia

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-11-17 08:08:01 Re: virtual generated column as partition key
Previous Message Richard Guo 2025-11-17 07:28:45 Re: Use exact nullingrels matches for NestLoopParams