| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | hubert depesz lubaczewski <depesz(at)gmail(dot)com> |
| Cc: | cbbrowne(at)acm(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: request for feature: psql 'DSN' option |
| Date: | 2006-07-08 19:23:09 |
| Message-ID: | 44B0061D.9070909@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
hubert depesz lubaczewski wrote:
> On 7/7/06, *Andrew Dunstan* <andrew(at)dunslane(dot)net
> <mailto:andrew(at)dunslane(dot)net>> wrote:
>
> Why is this better than using the service file?
>
>
>
> service file is not well described in manual. quick grep showed that
> we have PGSERVICE variable, and pg_service.conf.sample, which doesn't
> even include all possible parameter names.
> and - comments in this file suggest it is to be used globally only:
> "Copy this to your sysconf directory (typically /usr/local/pgsql/etc)
> and...", and not "per user".
> i would really love to see pg_service.conf extended in such a way that
> i could:
> 1. store it in $HOME/.pg_service.conf
> 2. use name of service on psql invocation (not as env variable).
> preferably using psql service_name. this will conflict with current
> behaviour (treating argument as dbname), but with some basic logic, i
> belive it can be done.
>
The service file location is runtime configurable Just set PGSYSCONFDIR.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2006-07-08 21:47:33 | Re: lastval exposes information that currval does not |
| Previous Message | Diogo Biazus | 2006-07-08 18:50:56 | Re: xlog viewer prototype and new proposal |