Re: Pgoutput not capturing the generated columns

Peter Smith <smithpb2250@gmail.com>

From: Peter Smith <smithpb2250@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: vignesh C <vignesh21@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Michael Paquier <michael@paquier.xyz>, "Shinoda, Noriyoshi (SXD Japan FSIP)" <noriyoshi.shinoda@hpe.com>, Shubham Khanna <khannashubham1197@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Rajendra Kumar Dangwal <dangwalrajendra888@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, "euler@eulerto.com" <euler@eulerto.com>
Date: 2025-01-23T03:48:41Z
Lists: pgsql-hackers

Attachments

Hi Vignesh,

Patch v55-0002 (the docs chapter one) is a re-badged v54-0005.

I've addressed the PeterE review comments [1] as detailed below.:

FYI, because v55-0001 was broken I have posted this DOCS patch
separately. Please add it back into the patch set as vXX-0002 when you
next post it.


On Thu, Jan 23, 2025 at 12:52 AM Peter Eisentraut <peter@eisentraut.org> wrote:
>
> A few quick comments on the v54-0005 patch (the documentation one):
>
> +<programlisting>
> +test_pub=# CREATE TABLE tab_gen_to_gen (a int, b int GENERATED ALWAYS
> AS (a + 1) STORED);
>
> I don't like when examples include the prompt like this.  Then it's
> harder to copy the commands out of the examples.
>

I didn't remove all of these prompts because for logical replication
they add value by differentiating which pub/sub node the command is
run on. Also, these prompts are consistent with all other sections of
Chapter 29 -- e.g. see "Row filters", "Column Lists", and more.

OTOH, I did remove all the "continuation" prompts, so now command
cut/copy is easy.

> +     <row>
> +
> <entry>No</entry><entry>GENERATED</entry><entry>GENERATED</entry><entry>Publisher
> table column is not replicated. Use the subscriber table generated
> column value.</entry>
> +     </row>
>
> This should be formatted vertically, one line per <entry>.
>

Fixed.

> +<programlisting>
> +test_pub=# CREATE TABLE t1 (a int PRIMARY KEY, b int,
> +test_pub(#                  c int GENERATED ALWAYS AS (a + 1) STORED,
> +test_pub(#                  d int GENERATED ALWAYS AS (b + 1) STORED);
>
> Also here check that this is formatted more consistently with the rest
> of the documentation.
>

I modified it to put every column on a separate line (e.g. same
formatting as examples on the CREATE TABLE page). As mentioned above,
the continuation prompts are also removed now.

> +  <itemizedlist>
> +   <listitem><para>
> +    <literal>t1.a</literal> is a regular column. It gets replicated
> normally.
> +   </para></listitem>
> +   <listitem><para>
> +    <literal>t1.b</literal> is a regular column. It gets replicated
> normally.
> +   </para></listitem>
>
> Leave more whitespace.  Typically, there is a blank line between block
> elements on the same level.
>

Fixed.

======
[1] PeterE v54-0005 review -
https://www.postgresql.org/message-id/18f56f71-ea01-41aa-811e-367b692e9ca4%40eisentraut.org

Kind Regards,
Peter Smith.
Fujitsu Australia

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Doc: Generated column replication.

  2. Rename pubgencols_type to pubgencols in pg_publication.

  3. Doc: Fix column name in pg_publication catalog.

  4. Fix buildfarm failure introduced by commit e65dbc9927.

  5. Change publication's publish_generated_columns option type to enum.

  6. Fix \dRp+ output when describing publications with a lower server version.

  7. Replicate generated columns when 'publish_generated_columns' is set.

  8. Doc: Update the behavior of generated columns in Logical Replication.

  9. Replicate generated columns when specified in the column list.

  10. Doc: Generated columns are skipped for logical replication.