| From: | James Coleman <jtc331(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | radek(at)salac(dot)org, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16741: Error: subplan "SubPlan 1" was not initialized |
| Date: | 2020-11-29 13:21:52 |
| Message-ID: | CAAaqYe8JcHYnp1g85Ssf03MO2SETm-GwoMn7y7oAaRYZYPe7XQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Nov 23, 2020 at 5:39 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radek Salač | 2020-11-29 22:28:35 | Re: BUG #16741: Error: subplan "SubPlan 1" was not initialized |
| Previous Message | Alexander Lakhin | 2020-11-29 06:00:00 | Re: BUG #16750: VACUUM sporadically fails to access pgstat on Cygwin |