Re: Docs for service file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: 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 18:00:53
Message-ID: 15354.1041962453@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Well, it seems like a nifty features. What do others think? It allows
> centralized connection parameters.

It seems quite bogus to me: what good is a configuration file on the
server machine to clients on other machines? (And if it's not on the
server, one can hardly call it centralized.)

A proper design for such a feature would pass the service name as part
of the startup packet and let the postmaster fill in missing fields
using a server-side config file. Then it would be useful for local
and remote clients alike.

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.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-01-07 18:05:48 Re: Docs for service file
Previous Message Peter Eisentraut 2003-01-07 17:36:36 Re: Docs for service file