| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers-win32(at)postgresql(dot)org, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "T(dot)J(dot)" <tjtoocool(at)phreaker(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] More SSL questions.. |
| Date: | 2005-01-10 13:19:25 |
| Message-ID: | 11005.1105363165@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> Personally, I don't really care :-) My point was that ".pgpass" is bad.
> "pgpass" or "pgpass.conf" or "pgpass.txt" are all fine by me. I agree
> that .conf might be more logical than .txt.
I think the analogy to .conf is bogus. The existing files named .conf
are server config not client config, and they don't have leading dots
in their names on Unix either.
Also, the whole point of this exercise is to make these files easy to
edit for newbies. The fact that an association *could* be configured
for .conf seems to me to miss the point: anyone who knows enough to do
that wouldn't have a problem with any spelling whatever...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-01-10 15:39:36 | Re: [HACKERS] [BUGS] More SSL questions.. |
| Previous Message | Michael Meskes | 2005-01-10 13:00:41 | CVS commit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-01-10 15:39:36 | Re: [HACKERS] [BUGS] More SSL questions.. |
| Previous Message | Magnus Hagander | 2005-01-10 09:21:28 | Re: [BUGS] More SSL questions.. |