pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Julien Rouhaud <rjuju123@gmail.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Kevin Grittner <kgrittn@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Subject: Re: Add parallelism and glibc dependent only options to reindexdb
Date: Fri, 5 Jul 2019 18:22:19 +0200
Message-ID: <2b1504ac-3d6c-11ec-e1ce-3daf132b3d37@2ndquadrant.com> (raw)
In-Reply-To: <CAOBaU_ZuVqBr1BLrEDLRt1Bp_aF_F9ShM+uy=ePLWm9L9cnDYw@mail.gmail.com>
References: <CAOBaU_YrnH_Jqo46NhaJ7uRBiWWEcS40VNRQxgFbqYo9kApUsg@mail.gmail.com>
	<20190702082804.e7qgfncsyvxpcgra@development>
	<CAOBaU_ZuVqBr1BLrEDLRt1Bp_aF_F9ShM+uy=ePLWm9L9cnDYw@mail.gmail.com>

On 2019-07-02 10:45, Julien Rouhaud wrote:
> It just seemed wrong to me to allow a partial processing for something
> that's aimed to prevent corruption.  I'd think that if users are
> knowledgeable enough to only reindex a subset of indexes/tables in
> such cases, they can also discard indexes that don't get affected by a
> collation lib upgrade.  I'm not strongly opposed to supporting if
> though, as there indeed can be valid use cases.

We are moving in this direction.  Thomas Munro has proposed an approach
for tracking collation versions on a per-object level rather than
per-database.  So then we'd need a way to reindex not those indexes
affected by collation but only those affected by collation and not yet
fixed.

One could also imagine a behavior where not-yet-fixed indexes are simply
ignored by the planner.  So the gradual upgrading approach that Tomas
described is absolutely a possibility.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (78+ messages)  latest in thread

Message-ID: <2b1504ac-3d6c-11ec-e1ce-3daf132b3d37@2ndquadrant.com>
Permalink:  ../2b1504ac-3d6c-11ec-e1ce-3daf132b3d37@2ndquadrant.com/
Also on:    postgresql.org/message-id/2b1504ac-3d6c-11ec-e1ce-3daf132b3d37@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, rjuju123@gmail.com, tomas.vondra@2ndquadrant.com, pgsql-hackers@lists.postgresql.org, kgrittn@gmail.com, michael@paquier.xyz
  Subject: Re: Add parallelism and glibc dependent only options to reindexdb
  In-Reply-To: <2b1504ac-3d6c-11ec-e1ce-3daf132b3d37@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox