Re: Assertion failure in HEAD and 13 after calling COMMIT in a stored proc

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Jim Nasby <nasbyj(at)amazon(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Assertion failure in HEAD and 13 after calling COMMIT in a stored proc
Date: 2021-06-23 04:25:18
Message-ID: 20210623042518.GM29179@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 23, 2021 at 12:07:11AM -0400, Tom Lane wrote:
> Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> > This causes the server to crash during FETCH.
>
> > ts=# begin; declare b cursor for VALUES(1); fetch 100 in b;
> > BEGIN
> > DECLARE CURSOR
> > server closed the connection unexpectedly
> > This probably means the server terminated abnormally
> > before or while processing the request.
> > The connection to the server was lost. Attempting reset: Failed.
>
> Hm, works for me:

I think it's because I had old pg_stat_statements module, and hadn't make -C contrib.

Sorry for the noise.

--
Justin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2021-06-23 04:37:30 Automatic notification for top transaction IDs
Previous Message houzj.fnst@fujitsu.com 2021-06-23 04:16:10 Partition Check not updated when insert into a partition