Re: BUG #16741: Error: subplan "SubPlan 1" was not initialized - Mailing list pgsql-bugs

From James Coleman
Subject Re: BUG #16741: Error: subplan "SubPlan 1" was not initialized
Date
Msg-id CAAaqYe8JcHYnp1g85Ssf03MO2SETm-GwoMn7y7oAaRYZYPe7XQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16741: Error: subplan "SubPlan 1" was not initialized  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #16741: Error: subplan "SubPlan 1" was not initialized  (Radek Salač <radek@salac.org>)
List pgsql-bugs
On Mon, Nov 23, 2020 at 5:39 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> PG Bug reporting form <noreply@postgresql.org> writes:
> > I'm getting error:
>
> > ERROR: subplan "SubPlan 1" was not initialized
> > CONTEXT: parallel worker
>
> Yeah, this is a known issue that we haven't yet fixed, cf [1].
>
> I believe you should be able to work around it for now
> by turning off enable_incremental_sort.
>
>                         regards, tom lane
>
> [1] https://www.postgresql.org/message-id/flat/622580997.37108180.1604080457319.JavaMail.zimbra%40siscobra.com.br


That might workaround it for 13/13.1, though the attached plan has a
sort, not an incremental sort, and so it's possible that won't help
(disabling parallel query for this particular query would then
resolve, but that's a fairly large sledgehammer).

A fix is being discussed in [1].

James

1: https://www.postgresql.org/message-id/flat/CAAaqYe8cK3g5CfLC4w7bs%3DhC0mSksZC%3DH5M8LSchj5e5OxpTAg%40mail.gmail.com



pgsql-bugs by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: BUG #16750: VACUUM sporadically fails to access pgstat on Cygwin
Next
From: Radek Salač
Date:
Subject: Re: BUG #16741: Error: subplan "SubPlan 1" was not initialized