Re: Pgoutput not capturing the generated columns
От | Peter Smith |
---|---|
Тема | Re: Pgoutput not capturing the generated columns |
Дата | |
Msg-id | CAHut+PtVfrbx0jb42LCmS=-LcMTtWxm+vhaoArkjg7Z0mvuXbg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Pgoutput not capturing the generated columns (Shubham Khanna <khannashubham1197@gmail.com>) |
Ответы |
Re: Pgoutput not capturing the generated columns
|
Список | pgsql-hackers |
Hi Shubham. Thanks for separating the new BMS 'columns' modification. Here are my review comments for the latest patch v17-0001. ====== 1. src/backend/replication/pgoutput/pgoutput.c /* * Columns included in the publication, or NULL if all columns are * included implicitly. Note that the attnums in this bitmap are not + * publication and include_generated_columns option: other reasons should + * be checked at user side. Note that the attnums in this bitmap are not * shifted by FirstLowInvalidHeapAttributeNumber. */ Bitmapset *columns; With this latest 0001 there is now no change to the original interpretation of RelationSyncEntry BMS 'columns'. So, I think this field comment should remain unchanged; i.e. it should be the same as the current HEAD comment. ====== src/test/subscription/t/011_generated.pl nitpick - comment changes for 'tab2' and 'tab3' to make them more consistent. ====== 99. Please refer to the attached diff patch which implements any nitpicks described above. ====== Kind Regards, Peter Smith. Fujitsu Australia
Вложения
В списке pgsql-hackers по дате отправления: