Re: database aliasing options ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Gauthier <davegauthierpg(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: database aliasing options ?
Date: 2020-11-09 15:49:52
Message-ID: 1983183.1604936992@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Gauthier <davegauthierpg(at)gmail(dot)com> writes:
> Our IT dept has configured our PG DB as a "High Availability" database. It
> has a primary and backup server (disks too). Normally both are running but
> if one goes down, the other is still available for use, effectively keeping
> the DB up while the failed server is being repaired.

> My question has to do with creating and using a DB alias for DB connection
> code. Of course the idea would be to toggle which server the alias is
> pointing to based on the state of the servers. The idea is to manage which
> server is being used OUTSIDE of the DB connection code by changing the
> alias. The code always uses the alias.

Some people do this by changing the DNS entry for the server.

Another thought is that maybe you don't have to do anything dynamic,
if you set up the clients with host lists not just single hostnames
(that is, "-h host1,host2" or the equivalent). That should work for
any libpq-based client.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message mark armon 2020-11-09 16:08:21 How to set up a schema default date to '2020-01-01'?
Previous Message David Gauthier 2020-11-09 15:24:04 database aliasing options ?