Horton

Re: Avoid full GIN index scan when possible

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>, Nikita Glukhov <n.gluhov@postgrespro.ru>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Julien Rouhaud <rjuju123@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, Marc Cousin <cousinmarc@gmail.com>
Date: 2020-01-10T15:31:30Z
Lists: pgsql-hackers 
Alexander Korotkov <a.korotkov@postgrespro.ru> writes:
> So, I think v10 is a version of patch, which can be committed after
> some cleanup.  And we can try doing better nulls handling in a separate
> patch.

The cfbot reports that this doesn't pass regression testing.
I haven't looked into why not.

			regards, tom lane

Commits

  1. Avoid full scan of GIN indexes when possible