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

From Tom Lane
Subject Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql
Date
Msg-id 8218.1507252586@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when calledfrom inside pl/pgsql  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
Andres Freund <andres@anarazel.de> writes:
> On 2017-10-05 19:42:30 -0400, Tom Lane wrote:
>> https://www.postgresql.org/message-id/26365.1162532453%40sss.pgh.pa.us

> 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.

Nah; that presupposes that if a subquery runs out of memory then the
surrounding function is necessarily broken.  I don't buy that.
        regards, tom lane


-- 
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: ben m
Date:
Subject: Re: [BUGS] BUG #14843: CREATE TABLE churns through all memory,crashes db
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] BUG #14843: CREATE TABLE churns through all memory,crashes db