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

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Christoph Berg <myon@debian.org>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Collation versioning
Date: Thu, 27 Sep 2018 23:19:26 +0200
Message-ID: <b4ae8ef0-3a32-0f9a-576b-8f53ddbdc56d@2ndquadrant.com> (raw)
In-Reply-To: <CAEepm=33gHF92UD8bkoZzzbs+GkVhHFzgV4CPf8ZxFRqZ_UCHQ@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>
	<b7ce31bb-dfe5-c689-06c4-3a8536f73e6a@2ndquadrant.com>
	<CAEepm=01SJne1beXkuU0XxO3UdoG+n+BaE9X_ADXjG95s0nqbQ@mail.gmail.com>
	<CAEepm=1xGTsLDx63UEdcJ8MdG63CNJ-tsDWHbH9djtvxRH5ZWw@mail.gmail.com>
	<20180912081547.GA24584@msg.df7cb.de>
	<0447ec7b-cdb6-7252-7943-88a4664e7bb7@2ndquadrant.com>
	<20180912112548.GC24584@msg.df7cb.de>
	<4f60612c-a7b5-092d-1532-21ff7a106bd5@2ndquadrant.com>
	<CAEepm=33gHF92UD8bkoZzzbs+GkVhHFzgV4CPf8ZxFRqZ_UCHQ@mail.gmail.com>

On 16/09/2018 10:19, Thomas Munro wrote:
> 4.  After creating a new database, update that row as appropriate in
> the new database (!).  Or find some other way to write a new table out
> and switch it around, or something like that.  That is, if you say
> CREATE DATABASE foo LC_COLLATE = 'xx_XX', COLLATION_PROVIDER = libc
> then those values somehow get written into the default pg_collation
> row in the *new* database (so at that point it's not a simple copy of
> the template database).

I've been hatching this exact scheme since the very beginning, even
thinking about using the background session functionality to do this.
It would solve a lot of problems, but there is the question of exactly
how to do that "(!)" part.

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




view thread (188+ messages)  latest in thread

Message-ID: <b4ae8ef0-3a32-0f9a-576b-8f53ddbdc56d@2ndquadrant.com>
Permalink:  ../b4ae8ef0-3a32-0f9a-576b-8f53ddbdc56d@2ndquadrant.com/
Also on:    postgresql.org/message-id/b4ae8ef0-3a32-0f9a-576b-8f53ddbdc56d@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, thomas.munro@enterprisedb.com, myon@debian.org
  Subject: Re: Collation versioning
  In-Reply-To: <b4ae8ef0-3a32-0f9a-576b-8f53ddbdc56d@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