Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when calledfrom inside pl/pgsql - Mailing list pgsql-bugs

From Andres Freund
Subject Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when calledfrom inside pl/pgsql
Date
Msg-id 20171006005915.lyivbm6fplmbmon2@alap3.anarazel.de
Whole thread Raw
In response to Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2017-10-05 19:42:30 -0400, Tom Lane wrote:
> I dug around in the archives and found

Ah thanks.

> https://www.postgresql.org/message-id/26365.1162532453%40sss.pgh.pa.us
> 
> The function shown there doesn't appear to leak any memory at all in HEAD,
> but if you dike out the memory context reset in question, it leaks like
> crazy.  I didn't try to reconfirm my old estimate of 16KB per iteration,
> but it seemed to be in that ballpark still.

Just ran this, got out-of-memory error, and then another out-of-memory
error, ...  I wonder if we should exclude out_of_memory from OTHERS,
like we do QUERY_CANCELED and ASSERT_FAILURE.

(looking)

Greetings,

Andres Freund


-- 
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: Tom Lane
Date:
Subject: Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] BUG #14843: CREATE TABLE churns through all memory,crashes db