Re: Avoid full GIN index scan when possible

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Marc Cousin <cousinmarc(at)gmail(dot)com>
Subject: Re: Avoid full GIN index scan when possible
Date: 2020-01-17 21:34:47
Message-ID: CAPpHfdvx9Ec60Jq5dH-YyPvasAhPpJqtDmtabXAigxwGq=n4=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 18, 2020 at 12:33 AM Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> So, I think we don't need so huge regression test to exercise this corner case.

Forgot to mention. I'm going to push v15 if no objections.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-01-17 21:35:46 Re: Crash in BRIN summarization
Previous Message Robert Haas 2020-01-17 21:33:48 Re: making the backend's json parser work in frontend code