From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | anderson <anderson2013(at)qq(dot)com> |
Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen |
Date: | 2016-12-27 05:29:44 |
Message-ID: | CAB7nPqR5+3gLAedjfDVUQPGz-SBwtOwNn6QMPkecVud7pg=NgQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Dec 27, 2016 at 12:30 PM, anderson <anderson2013(at)qq(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2016-12-27 09:40:39 | Re: pg_receivexlog creating holes in WAL (HEAD only) |
Previous Message | anderson | 2016-12-27 03:30:47 | [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen |