|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>|
|Cc:||Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: REINDEX filtering in the backend|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Wed, Sep 04, 2019 at 01:54:53PM +0200, Peter Eisentraut wrote:
> Right. We should aim to get per-object collation version tracking done.
> And then we might want to have a REINDEX variant that processes exactly
> those indexes with an out-of-date version number -- and then updates
> that version number once the reindexing is done. I think that project
> is achievable for PG13.
> I think we can keep this present patch in our back pocket for, say, the
> last commit fest if we don't make sufficient progress on those other
> things. Right now, it's hard to review because the target is moving,
> and it's unclear what guidance to give users.
Okay, agreed. I have marked the patch as returned with feedback
|Next Message||Michael Paquier||2019-09-06 05:01:42||Re: Plug-in common/logging.h with vacuumlo and oid2name|
|Previous Message||Tom Lane||2019-09-06 03:49:03||Re: [bug fix] Produce a crash dump before main() on Windows|