Re: REINDEX filtering in the backend

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REINDEX filtering in the backend
Date: 2019-08-30 00:10:16
Message-ID: 20190830001016.GA1892@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 29, 2019 at 10:52:55AM +0200, Julien Rouhaud wrote:
> That was already suggested by Thomas and seconded by Peter E., see
> https://www.postgresql.org/message-id/2b1504ac-3d6c-11ec-e1ce-3daf132b3d37%402ndquadrant.com.
>
> I personally think that it's a sensible approach, and I'll be happy to
> propose a patch for that too if no one worked on this yet.

That may be interesting to sort out first then because we'd likely
want to know what is first in the catalogs before designing the
filtering processing looking at it, no?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message keisuke kuroda 2019-08-30 02:48:47 Re: Wrong value in metapage of GIN INDEX.
Previous Message Peter Geoghegan 2019-08-30 00:07:53 Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.