> -----Original Message-----
> From: Florian Weimer [mailto:fweimer@bfk.de]
> Sent: Wednesday, August 24, 2011 5:00 AM
> To: Gabriele Bartolini
> Cc: pgsql-admin@postgresql.org
> Subject: Re: Database alias
>
> * 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
PgBouncer is the easiest piece of software to install and to manage I've ever dealt with, and it's very light on system
resources.
Regards,
Igor Neyman
