agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedFrom: Christoph Berg <myon@debian.org>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Collation versioning
Date: Fri, 28 Sep 2018 09:24:50 +0200
Message-ID: <20180928072450.GA26142@msg.df7cb.de> (raw)
In-Reply-To: <CAEepm=0EVCF_Nj5uYV5f6xH34MK1Z4mCfb+Svn1yJ_zsx5tOFw@mail.gmail.com>
References: <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>
<b4ae8ef0-3a32-0f9a-576b-8f53ddbdc56d@2ndquadrant.com>
<CAEepm=0EVCF_Nj5uYV5f6xH34MK1Z4mCfb+Svn1yJ_zsx5tOFw@mail.gmail.com>
Re: Thomas Munro 2018-09-27 <CAEepm=0EVCF_Nj5uYV5f6xH34MK1Z4mCfb+Svn1yJ_zsx5tOFw@mail.gmail.com>
> > > 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.
> >
> > 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.
Making (!) work would also allow reassigning the "public" schema to
the database owner. That would fix that gross security gap that is
left with the default search_path, while still keeping usability. It
would make a whole lot of sense to work on making this feasible.
Christoph
view thread (188+ messages) latest in thread
Message-ID: <20180928072450.GA26142@msg.df7cb.de>
Permalink: ../20180928072450.GA26142@msg.df7cb.de/
Also on: postgresql.org/message-id/20180928072450.GA26142@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@enterprisedb.com, peter.eisentraut@2ndquadrant.com
Subject: Re: Collation versioning
In-Reply-To: <20180928072450.GA26142@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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox