From: Florian Weimer <fweimer@bfk.de>
To: Gabriele Bartolini <Gabriele.Bartolini@2ndQuadrant.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: Database alias
Date: Wed, 24 Aug 2011 08:59:46 +0000
Message-ID: <82aaazkwvx.fsf@mid.bfk.de> (raw)
In-Reply-To: <fa646e9b1300e2a180de9bd11e133a5e@2ndquadrant.it>
References: <82ippnky8l.fsf@mid.bfk.de>
<fa646e9b1300e2a180de9bd11e133a5e@2ndquadrant.it>
* Gabriele Bartolini:
> On Wed, 24 Aug 2011 08:30:34 +0000, Florian Weimer <fweimer@bfk.de>
> wrote:
>> We've got some systems which use a historic database name and would
>> like to transition them to our current naming scheme. Is there
>> support for some form of database aliases?
>
> If you are trying to make the database seen by clients under a
> different name, probably the most practical solution would be to add a
> PgBouncer layer in front of the clients which maps the old database
> name to the new one.
>
> http://wiki.postgresql.org/wiki/PgBouncer
Ah, that would probably work at a technical level, thanks. But in this
particular case, my aim is to avoid additional complexity, and
installing PgBouncer seems to be at odds with this goal. 8-)
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
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-admin@postgresql.org
Cc: fweimer@bfk.de, Gabriele.Bartolini@2ndQuadrant.it
Subject: Re: Database alias
In-Reply-To: <82aaazkwvx.fsf@mid.bfk.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