Re: Data is copied twice when specifying both child and parent table in publication
От | Peter Smith |
---|---|
Тема | Re: Data is copied twice when specifying both child and parent table in publication |
Дата | |
Msg-id | CAHut+PuGadw7LFfCahPE10HSRCd2L+zbAQcP_GM9B-8LwajR4g@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Data is copied twice when specifying both child and parent table in publication ("wangw.fnst@fujitsu.com" <wangw.fnst@fujitsu.com>) |
Ответы |
Re: Data is copied twice when specifying both child and parent table in publication
|
Список | pgsql-hackers |
A minor review comment for v25-0001. ====== src/backend/commands/subscriptioncmds.c 1. @@ -1936,21 +1936,56 @@ fetch_table_list(WalReceiverConn *wrconn, List *publications) WalRcvExecResult *res; StringInfoData cmd; TupleTableSlot *slot; - Oid tableRow[3] = {TEXTOID, TEXTOID, NAMEARRAYOID}; + Oid tableRow[3] = {TEXTOID, TEXTOID, InvalidOid}; The patch could be slightly less invasive if you did not make this change, but instead, only overwrite tableRow[2] for the >= PG16 case. Or vice versa, if you prefer. The point is, there are only 2 cases, so you might as well initialize a default tableRow[2] that is valid for one case and overwrite it only for the other case, instead of overwriting it in 2 places. YMMV. ------ Kind Regards, Peter Smith. Fujitsu Australia
В списке pgsql-hackers по дате отправления: