BUG #13470: Logical replication 'invalid memory alloc'

From: kotlarski(dot)krzysztof(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13470: Logical replication 'invalid memory alloc'
Date: 2015-06-26 10:03:33
Message-ID: 20150626100333.3874.90852@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 13470
Logged by: Krzysztof Kotlarski
Email address: kotlarski(dot)krzysztof(at)gmail(dot)com
PostgreSQL version: 9.4.4
Operating system: Tested OS X and Gentoo
Description:

Minimal reproductible example:

SELECT * FROM pg_create_logical_replication_slot('test_slot',
'test_decoding');
CREATE TABLE "t" ("a" character varying);
ALTER TABLE "t" REPLICA IDENTITY FULL;
INSERT INTO "t" ("a") VALUES ('a1');
ALTER TABLE "t" ADD "b" character varying;
UPDATE "t" SET "a" = 'a2';
SELECT * FROM pg_logical_slot_get_changes('test_slot', NULL, NULL);

Produces:
slot_name | xlog_position
-----------+---------------
test_slot | 6/BD3C1950
(1 row)

CREATE TABLE
ALTER TABLE
INSERT 0 1
ALTER TABLE
UPDATE 1
ERROR: invalid memory alloc request size 18446744073709551613
CONTEXT: slot "test_slot", output plugin "test_decoding", in the change
callback, associated LSN 6/BD3D8C28

Bug affects all 9.4 versions.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message andomar 2015-06-26 10:25:41 BUG #13471: Reload with include_dir results in incorrect "contains errors" message
Previous Message Michael Paquier 2015-06-26 05:50:05 Re: Re: windows 8 RTM compatibility issue (could not reserve shared memory region for child)