The following bug has been logged on the website:
Bug reference: 14471
Logged by: Josef Machytka
Email address: josef.machytka@gmail.com
PostgreSQL version: 9.6.1
Operating system: Debian jessie
Description:
I checked stackoverflow and I found several questions complaining about
problems with "NOT IN" causing problems in selects.
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.
It is also possible that problem happens only when working with partitioned
tables. We have several sets of partitioned tables. Partitions are by months
- data are used for billing calculations.
Our select which crashes pg 9.6 is like this:
select <some columns>
from table_1_partition t1
inner join table_2 t2 --also partitioned table
on ....
where (t1.col1, t2.col1, t1.col2) NOT IN
(select col1, col2, col3
from table_3 --also partitioned table
group by col1, col2, col3)
When I remove NOT IN part everything works OK. Of course I replaced this
problematic part with NOT EXISTS construct. But "unknown error" crash with
"NOT IN" command is very unfortunate.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
