pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Christoph Berg <myon@debian.org>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Collation versioning
Date: Fri, 11 Oct 2019 12:48:14 +0200
Message-ID: <20191011104813.GA14059@msg.df7cb.de> (raw)
In-Reply-To: <CA+hUKGKDe98DFWKJoS7e4Z+Oamzc-1sZfpL3V3PPgi1uNvQ1tw@mail.gmail.com>
References: <CAEepm=0hoACQLFn8ro7jCO9-wTth2mXXS3K=s09gxKqN2jy8pA@mail.gmail.com>
	<CAEepm=3a5BC7CwsXZo3V4fw6YuAMT2nJ1krwtqOatb=vDqRWEA@mail.gmail.com>
	<20180905191014.GA29241@msg.df7cb.de>
	<CAEepm=3mKYhXS9NQCsPkGhkQxKAeZwbDneZV7QYKTDDYstTxZA@mail.gmail.com>
	<4b76c6d4-ae5e-0dc6-7d0d-b5c796a07e34@2ndquadrant.com>
	<CA+hUKGKewJO4Cb4G_p5Mu7M5fSFSRg1aWXK6aTXHoY0HMMwWtg@mail.gmail.com>
	<7c039a8a-2be4-b4f3-48d2-c5c7d24dd98b@2ndquadrant.com>
	<2df246f1-a1f5-8344-9100-be53736f68c0@2ndquadrant.com>
	<CA+hUKGKDe98DFWKJoS7e4Z+Oamzc-1sZfpL3V3PPgi1uNvQ1tw@mail.gmail.com>

Re: Thomas Munro 2019-10-11 <CA+hUKGKDe98DFWKJoS7e4Z+Oamzc-1sZfpL3V3PPgi1uNvQ1tw@mail.gmail.com>
> While testing pg_upgrade scenarios I noticed that initdb-created
> collations' versions are not preserved, potentially losing track of
> information about corrupted indexes.  That's a preexisting condition,
> and probably well understood, but it made me realise that if we switch
> to per-database object (for example: per index) version tracking as
> mentioned up-thread, then we should probably preserve that information
> across pg_upgrade.

That would make much sense, yes. The whole problem is already complex
enough, if we add another "but if you use pg_upgrade, you still need
to do the tracking manually" footnote, users will be very confused.

Christoph





view thread (188+ messages)  latest in thread

Message-ID: <20191011104813.GA14059@msg.df7cb.de>
Permalink:  ../20191011104813.GA14059@msg.df7cb.de/
Also on:    postgresql.org/message-id/20191011104813.GA14059@msg.df7cb.de

 · 

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: myon@debian.org, thomas.munro@gmail.com, peter.eisentraut@2ndquadrant.com
  Subject: Re: Collation versioning
  In-Reply-To: <20191011104813.GA14059@msg.df7cb.de>

* 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