Re: ResourceOwner refactoring - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: ResourceOwner refactoring
Date
Msg-id e56be7d9-14b1-664d-0bfc-00ce9772721c@gmail.com
Whole thread Raw
In response to Re: ResourceOwner refactoring  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: ResourceOwner refactoring
List pgsql-hackers
Hello Heikki,

I've stumbled upon yet another anomaly introduced with b8bff07da.

Please try the following script:
SELECT 'init' FROM pg_create_logical_replication_slot('slot',
   'test_decoding');
CREATE TABLE tbl(t text);
BEGIN;
TRUNCATE table tbl;

SELECT data FROM pg_logical_slot_get_changes('slot', NULL, NULL,
  'include-xids', '0', 'skip-empty-xacts', '1', 'stream-changes', '1');

On b8bff07da (and the current HEAD), it ends up with:
ERROR:  ResourceOwnerEnlarge called after release started

But on the previous commit, I get no error:
  data
------
(0 rows)

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: "a.kozhemyakin"
Date:
Subject: pltcl crashes due to a syntax error
Next
From: Tom Lane
Date:
Subject: Re: pltcl crashes due to a syntax error