On Wed, Sep 12, 2018 at 01:06:12PM +1200, Thomas Munro wrote: > The ideal scope would be to track all referenced collation versions on > every index, and only update them at CREATE INDEX or REINDEX time > (also, as discussed in some other thread, CHECK constraints and > partition keys might be invalidated and should in theory also carry > versions that can only be updated by running a hypothetical RECHECK or > REPARTITION command). Then a shared pg_collation catalog would make > perfect sense, and there would be no need for it to have a collversion > column at all, or an ALTER COLLATION ... REFRESH VERSION command, and > therefore there would be no way to screw it up by REFRESHing the > VERSION without having really fixed the problem.
Please note that the latest patch set does not apply, so this has been switched to commit fest 2018-11, waiting on author for a rebase. -- Michael
signature.asc
Description: PGP signature
