Re: pgsql: Store 2PC GID in commit/abort WAL recs for logical decoding

Поиск
Список
Период
Сортировка
От Nikhil Sontakke
Тема Re: pgsql: Store 2PC GID in commit/abort WAL recs for logical decoding
Дата
Msg-id CAMGcDxey6dG1DP34_tJMoWPcp5sPJUAL4K5CayUUXLQSx2GQpA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding  (Heikki Linnakangas <hlinnaka@iki.fi>)
Ответы Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения 
Hi Heikki,


>
> Pushed, thanks for the review!
>

There was a slight oversight in the twophase_gid length calculation in
the XactLogCommitRecord() code path in the cf5a1890592 commit. The
corresponding XactLogAbortRecord() code path was ok. PFA, a small
patch to fix the oversight.

Regards,
Nikhils
-- 
 Nikhil Sontakke                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
Вложения

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

Предыдущее
От: Surafel Temesgen
Дата:
Сообщение: Re: ON CONFLICT DO NOTHING on pg_dump
Следующее
От: David Rowley
Дата:
Сообщение: Re: why partition pruning doesn't work?