Re: Skipping schema changes in publication
| От | Peter Smith |
|---|---|
| Тема | Re: Skipping schema changes in publication |
| Дата | |
| Msg-id | CAHut+PuHn-hohA4OdEJz+Zfukfr41TvMTeTH7NwJ=wg1+94uNA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Skipping schema changes in publication (Shlok Kyal <shlok.kyal.oss@gmail.com>) |
| Список | 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
В списке pgsql-hackers по дате отправления: