From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Docs for service file |
Date: | 2003-01-09 21:50:26 |
Message-ID: | Pine.LNX.4.44.0301092110530.29178-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian writes:
> Tom Lane wrote:
> > Rather than documenting it and thereby locking ourselves into a
> > misdesigned "feature", I'd vote for removing code and docs too.
> > We can put the concept on the TODO-for-protocol-change list instead.
>
> Other votes?
I'm still looking for a reason to use this feature. Clearly, as it stands
it is only single-host. And on a single host you can use the environment
variables. Also, any reasonable application provides its own way to
encapsulate database connection information. And the other emails don't
convince me at all that this is somehow "Oracle-compatible".
Maybe you want to use ODBC, which gives you something like this and much
more.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-01-09 21:50:35 | Re: [HACKERS] PostgreSQL libraries - PThread Support, but |
Previous Message | Peter Eisentraut | 2003-01-09 21:48:15 | Re: more adequate usage msg: pg_controldata.diff |