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"
In-reply-to: <20161221094443.25614.47807@wrigleys.postgresql.org>
References: <20161221094443.25614.47807@wrigleys.postgresql.org>
Comments: In-reply-to josef.machytka@gmail.com
	message dated "Wed, 21 Dec 2016 09:44:43 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6817.1482333970.1@sss.pgh.pa.us>
Date: Wed, 21 Dec 2016 10:26:10 -0500
Message-ID: <6818.1482333970@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

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