Re: row filtering for logical replication
От | Alvaro Herrera |
---|---|
Тема | Re: row filtering for logical replication |
Дата | |
Msg-id | 202201112130.my5pj4m2cifc@alvherre.pgsql обсуждение исходный текст |
Ответ на | RE: row filtering for logical replication ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>) |
Ответы |
Re: row filtering for logical replication
Re: row filtering for logical replication |
Список | pgsql-hackers |
I just looked at 0002 because of Justin Pryzby's comment in the column filtering thread, and realized that the pgoutput row filtering has a very strange API, which receives both heap tuples and slots; and we seem to convert to and from slots in seemingly unprincipled ways. I don't think this is going to fly. I think it's OK for the initial entry into pgoutput to be HeapTuple (but only because that's what ReorderBufferTupleBuf has), but it should be converted a slot right when it enters pgoutput, and then used as a slot throughout. I think this is mostly sensible in 0001 (which was evidently developed earlier), but 0002 makes a nonsensical change to the API, with poor results. (This is one of the reasons I've been saying that there patches should be squashed together -- so that we can see that the overall API transformation we're making are sensible.) -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
В списке pgsql-hackers по дате отправления: