Re: Pgoutput not capturing the generated columns
Peter Smith <smithpb2250@gmail.com>
On Fri, Jan 24, 2025 at 12:03 AM Shinoda, Noriyoshi (SXD Japan FSI) <noriyoshi.shinoda@hpe.com> wrote: > > Hi, hackers. > > Thanks for developing this great feature. > The documentation for the pg_publication catalog shows a 'pubgencols' column, but the actual column name is the 'pubgencols_type' column. > Also, the order of the columns in the documentation differs from the order of the columns in the actual pg_publication catalog. > The attached patch changes the column names and order in the documentation. > Your catalog pg_publication docs fix patch does what it says and looked ok to me. However, in hindsight, I am not sure that the column should have been renamed 'pubgencols_type' in the first place because I cannot find any other catalogs with an underscore in their column names. Maybe 'pubgencolstype' or simply leaving it as 'pubgencols' would have been better? ====== Kind Regards, Peter Smith. Fujitsu Australia
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: Generated column replication.
- 6252b1eaf82b 18.0 landed
-
Rename pubgencols_type to pubgencols in pg_publication.
- 75eb9766ec20 18.0 landed
-
Doc: Fix column name in pg_publication catalog.
- 117f9f328e0f 18.0 landed
-
Fix buildfarm failure introduced by commit e65dbc9927.
- b35434b134b1 18.0 landed
-
Change publication's publish_generated_columns option type to enum.
- e65dbc9927fb 18.0 landed
-
Fix \dRp+ output when describing publications with a lower server version.
- 991974bb4888 18.0 landed
-
Replicate generated columns when 'publish_generated_columns' is set.
- 7054186c4ebe 18.0 landed
-
Doc: Update the behavior of generated columns in Logical Replication.
- 5b0c46ea0932 18.0 landed
-
Replicate generated columns when specified in the column list.
- 745217a051a9 18.0 landed
-
Doc: Generated columns are skipped for logical replication.
- 7a089f6e6a14 17.0 cited