Re: [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen
От | Michael Paquier |
---|---|
Тема | Re: [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen |
Дата | |
Msg-id | CAB7nPqR5+3gLAedjfDVUQPGz-SBwtOwNn6QMPkecVud7pg=NgQ@mail.gmail.com обсуждение исходный текст |
Ответ на | [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen ("anderson" <anderson2013@qq.com>) |
Ответы |
[BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen
|
Список | pgsql-bugs |
On Tue, Dec 27, 2016 at 12:30 PM, anderson <anderson2013@qq.com> wrote: > I found a postgresql 9.4.10 Logical decoding problem > heapam.c:6976 xlog store incorrect oldtuplen when tuplelen is greater than > the value field of uint16. > > a uint32 variable is assigned to uint16 > > The structure that holds the oldkey length is: > typedef struct xl_heap_header_len > { > uint16 t_len; > xl_heap_header header; > } xl_heap_header_len; > > The problem will lead to logic decoding failure when oldtuplene > 65535 and > relreplident = FULL. > The table that triggers the problem is usually relreplident = FULL. Do you have a test case able to reproduce the problem? -- Michael -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: