Re: Pgoutput not capturing the generated columns
Peter Smith <smithpb2250@gmail.com>
On Thu, Oct 3, 2024 at 10:09 AM Peter Smith <smithpb2250@gmail.com> wrote: > > Hi Shubham, > > The different meanings of the terms "parameter" versus "option" were > discussed in a recent thread [1], and that has made me reconsider this > generated columns feature. > > Despite being in the PUBLICATION section "WITH ( publication_parameter > [= value] [, ... ] )", I think that 'publish_generated_columns' is an > "option" (not a parameter). > > We should update all those places that are currently calling it a parameter: > - commit messages > - docs > - comments > - etc. > > ====== > [1] https://www.postgresql.org/message-id/CAHut%2BPuiRydyrYfMzR1OxOnVJf-_G8OBCLdyqu8jJ8si51d%2BEQ%40mail.gmail.com > It seems there are differing opinions on that other thread about what term to use. Probably, it is best to just leave the above suggestion alone for now. ====== 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