From: Tom Lane <tgl@sss.pgh.pa.us>
To: josef.machytka@gmail.com
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #14471: PostgreSQL 9.6 "NOT IN" in select causes crash with "ERROR: unknown error"
Date: Wed, 21 Dec 2016 10:26:10 -0500
Message-ID: <6818.1482333970@sss.pgh.pa.us> (raw)
In-Reply-To: <20161221094443.25614.47807@wrigleys.postgresql.org>
References: <20161221094443.25614.47807@wrigleys.postgresql.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
josef.machytka@gmail.com writes:
> Looks like PostgreSQL 9.6 now very probably has some bug connected with "NOT
> IN" command. We have select which actually crashes after several hours (!)
> of run with message "ERROR: unknown error". Although according to explain
> plan it should be done in ~40 minutes.
This is an interesting report, but without enough information to replicate
the problem, we're unlikely to be able to help you. A fragment of a
query, with zero information about the underlying tables, is far from
enough.
The only occurrences of the string "unknown error" that I can find in the
source code are in dblink and postgres_fdw (both reflecting cases where
the remote server did not return an error message, itself a "shouldn't
happen" situation). If you were using either, you didn't say so; but if
you were, maybe taking a look in the remote server's log would be useful.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, josef.machytka@gmail.com
Subject: Re: BUG #14471: PostgreSQL 9.6 "NOT IN" in select causes crash with "ERROR: unknown error"
In-Reply-To: <6818.1482333970@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox