Re: pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Ben Chobot <bench(at)silentmedia(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql
Date: 2017-10-06 01:16:26
Message-ID: 8218.1507252586@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2017-10-06 01:32:45 Re: BUG #14843: CREATE TABLE churns through all memory, crashes db
Previous Message ben m 2017-10-06 01:09:49 Re: BUG #14843: CREATE TABLE churns through all memory, crashes db