RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change

Поиск
Список
Период
Сортировка
Искать
От
Hayato Kuroda (Fujitsu)
Тема
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
Дата
в 04:44:05
Msg-id
OS9PR01MB1214992F75AE3FDD46A1FF463F5E42@OS9PR01MB12149.jpnprd01.prod.outlook.com
Ответ на
Список
Дерево обсуждения
[BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change Vishal Prasanna <vishal.g@zohocorp.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change Vishal Prasanna <vishal.g@zohocorp.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change Vishal Prasanna <vishal.g@zohocorp.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Dear Álvaro,

Thanks for pushing and sorry for the late reply.
I didn't notice that.

> I ended up pushing to 14 after all, after I noticed that the code in
> that branch is pretty much identical to what's in 15 -- it was only the
> test code that required a separate patch file.

Yes. Per my understanding, the test except PG14 used the row filter, it was
added in PG15. Instead it tried to publish changes from the non-exist publication.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

В списке pgsql-bugs по дате отправления
FAQ