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: | 2017-01-01 00:06:45 |
Message-ID: | CAB7nPqSGwWQ-d5eQkQpYGV+b8S5FqV+RokcQfdHb14Tf-tStFQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Dec 28, 2016 at 8:32 PM, anderson <anderson2013(at)qq(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-01-01 09:53:52 | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |
Previous Message | Magnus Hagander | 2016-12-31 12:27:46 | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |