From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Marko Kreen <markokr(at)gmail(dot)com>, jd(at)commandprompt(dot)com, Aidan Van Dyk <aidan(at)highrise(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: .ini support for .pgpass |
Date: | 2011-04-06 17:38:17 |
Message-ID: | 1302111497.3238.16.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On ons, 2011-04-06 at 09:47 -0400, Tom Lane wrote:
> Marko Kreen <markokr(at)gmail(dot)com> writes:
> > On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> >> 1. More understandable .pgpass format. Yes, I understand our standard
> >> format, most people won't. Like JoshB said, hard to debug.
>
> > How about allowing '#'-comments there and putting field
> > list into all templates, examples and manpages?
>
> > man 5 pgpass?
>
> > pgpass.sample?
>
> > IOW, do we need to change format or are we having documentation problem?
>
> +1 for seeing this as a documentation problem. I don't think that
> converting the file to .ini style is going to somehow make it
> magically easier to use --- people still have to understand it,
> and frankly .ini format is just another format that not everyone knows.
>
> #-comments seem like a fine idea.
But it would have to be the user that would put the comment in there,
since we can't really install a default file.
I think a man page would be the best documentation method for
in-the-moment reference.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2011-04-06 17:47:42 | Re: Windows build issues |
Previous Message | Dave Page | 2011-04-06 17:34:31 | Re: Windows build issues |