Re: Docs for service file

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Justin Clift <justin(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Docs for service file
Date: 2003-01-07 19:28:13
Message-ID: 200301071928.h07JSDq25250@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Joe Conway wrote:
> Bruce Momjian wrote:
> > Oh, so there is one central server with connection information.
> > Interesting. Might be easier to just NFS mount the pg_service.conf file
> > on all the machines.... at least easier for us. ;-)
> >
>
> The way this is used on Oracle (at least in my experience) is to distribute a
> "tnsnames.ora" file to all of your client machines. Our Oracle dba maintains a
> master copy in cvs, and distributes changes whenever he adds or moves an
> Oracle instance (equiv to a single PostgreSQL database).

> It's a pain to keep the file syncronized, but it is nice to be able to able to
> type "prod" or "proto" or whatever depending on the database you want to
> connect to, without having to remember the actual server name and port.

You need to use NFS readonly mounts.

So it seems you use something almost identical to our client-side
pg_service.conf file in Oracle.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2003-01-07 20:23:03 Re: Docs for service file
Previous Message Joe Conway 2003-01-07 19:06:06 Re: Docs for service file