Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel WM <dwilches(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
Date: 2020-03-23 22:05:02
Message-ID: 20200323220502.yzkkmisx4igmiwen@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2020-03-14 17:35:41 -0700, Andres Freund wrote:
> I think the only reason this issue doesn't have actually bad
> consequences is that we throw an error afterwards - which'll result in
> the executor tree not being used any further.
>
> I'm inclined to simply copy v12's approach of just ad-hoc creating a
> slot in those routines?

Pushed a commit doing so in 10, 11 and in a seperate commit added tests
to 10-master.

Greetings,

Andres Freund

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-03-23 22:31:23 BUG #16312: How to get last modified timestamp of password change for user in postgresql.
Previous Message Andres Freund 2020-03-23 18:53:30 Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006