| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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:06:06 |
| Message-ID: | 3E1B251E.1040502@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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.
I have never actually seen the Oracle Names Listener (i.e the central service
info server) functionality used (even though we have it). Not sure why.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-01-07 19:28:13 | Re: Docs for service file |
| Previous Message | Justin Clift | 2003-01-07 18:51:04 | Re: Docs for service file |