Horton
Menu

Re: Pgoutput not capturing the generated columns

Peter Smith <smithpb2250@gmail.com>

View thread
From: Peter Smith <smithpb2250@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Shubham Khanna <khannashubham1197@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Rajendra Kumar Dangwal <dangwalrajendra888@gmail.com>, pgsql-hackers@lists.postgresql.org, euler@eulerto.com
Date: 2024-11-06T04:55:48Z
Lists: pgsql-hackers 
On Wed, Nov 6, 2024 at 3:26 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Nov 6, 2024 at 7:34 AM Peter Smith <smithpb2250@gmail.com> wrote:
> >
> > Hi Vignesh,
> >
> > Here are my review comments for patch v49-0001.
> >
>
> I have a question on the display of this new parameter.
>
> postgres=# \dRp+
>                                       Publication pub_gen
>   Owner   | All tables | Inserts | Updates | Deletes | Truncates | Via
> root | Generated columns
> ----------+------------+---------+---------+---------+-----------+----------+-------------------
>  KapilaAm | f          | t       | t       | t       | t         | f        | t
> Tables:
>     "public.test_gen"
>
> The current theory for the display of the "Generated Columns" option
> could be that let's add new parameters at the end which sounds
> reasonable. The other way to look at it is how it would be easier for
> users to interpret. I think the value of the "Via root" option should
> be either after "All tables" or at the end as that is higher level
> table information than operations or column-level information. As
> currently, it is at the end, so "Generated Columns" should be added
> before.
>
> Thoughts?
>

FWIW, I've always felt the CREATE PUBLICATION parameters
publish
publish_via_root
publish_generated_columns

Should be documented (e.g. on CREATE PUBLICATION page) in alphabetical order:
publish
publish_generated_columns
publish_via_root

~

Following on from that. IMO it will make sense for the describe
(\dRp+) columns for those parameters to be in the same order as the
parameters in the documentation. So the end result would be the same
order as what you are wanting, even though the reason might be
different.

======
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.