Re: [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen
Date
Msg-id CAB7nPqSGwWQ-d5eQkQpYGV+b8S5FqV+RokcQfdHb14Tf-tStFQ@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen  ("anderson" <anderson2013@qq.com>)
Responses Re: [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen
List pgsql-bugs
On Wed, Dec 28, 2016 at 8:32 PM, anderson <anderson2013@qq.com> wrote:
> reproduce the step:
>
> 1. create table testcase(a int,b int,c text,d text);
>
> 2. ALTER TABLE ONLY testcase REPLICA IDENTITY FULL;
>
> 3. psql  -d postgres -p5559 -c "copy testcase from ‘/tmp/testcase.csv'
> DELIMITER E'\t'  csv QUOTE '''' ";
>
> 4. select
> pg_create_logical_replication_slot('logical_slot','test_decoding');
>
> --update one row
> 5. update testcase set b = 1;
>
> 6. select count(*) from
> pg_logical_slot_peek_binary_changes('logical_slot',NULL,NULL);
> ERROR:  compressed data is corrupt
> --The data length is incorrect and decompression fails

OK, I can see the problem. And I can see as well that things have been
tackled in this area with 9.5 thanks to commit 2c03216d...
--
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 by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile