Re: Pgoutput not capturing the generated columns
Shubham Khanna <khannashubham1197@gmail.com>
On Wed, Jul 10, 2024 at 4:22 AM Peter Smith <smithpb2250@gmail.com> wrote: > > Hi Shubham/Shlok, I was thinking some more about the suggested new > BitMapSet (BMS) idea of patch 0001 that changes the 'columns' meaning > to include generated cols also where necessary. > > I feel it is a bit risky to change lots of code without being 100% > confident it will still be in the final push. It's also going to make > the reviewing job harder if stuff gets added and then later removed. > > IMO it might be better to revert all the patches (mostly 0001, but > also parts of subsequent patches) to their pre-BMS-change ~v14* state. > Then all the BMS "improvement" can be kept isolated in a new patch > 0004. > > Some more reasons to split this off into a separate patch are: > > * The BMS change is essentially a redesign/cleanup of the code but is > nothing to do with the actual *functionality* of the new "generated > columns" feature. > > * Apart from the BMS change I think the rest of the patches are nearly > stable now. So it might be good to get it all finished so the BMS > change can be tackled separately. > > * By isolating the BMS change, then we will be able to see exactly > what is the code cost/benefit (e.g. removal of redundant code versus > adding new logic) which is part of the judgement to decide whether to > do it this way or not. > > * By isolating the BMS change, then it makes it convenient for testing > before/after in case there are any performance concerns > > * By isolating the BMS change, if some unexpected obstacle is > encountered that makes it unfeasible then we can just throw away patch > 0004 and everything else (patches 0001,0002,0003) will still be good > to go. As suggested, I have created a separate patch for the Bitmapset(BMS) idea of patch 0001 that changes the 'columns' meaning to include generated cols also where necessary. Please refer to the updated v17 Patches here in [1]. See [1] for the changes added. [1] https://www.postgresql.org/message-id/CAHv8RjJ0gAUd62PvBRXCPYy2oTNZWEY-Qe8cBNzQaJPVMZCeGA%40mail.gmail.com Thanks and Regards, Shubham Khanna.
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