Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] More SSL questions..

From: "Magnus Hagander" <mha(at)sollentuna(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>,<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 09:21:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-hackers-win32
> > Where are we on this?  I think Andrew and I both think *.txt is 
> > confusing.  We need to decide on Monday if we should change the 
> > current *.txt names.  We can either leave it unchanged, 
> remove *.txt, 
> > or change it to *.config.
> > >>> APPDATA/postgresql/pgpass.txt
> > >>> APPDATA/postgresql/psqlrc.txt
> Another idea is to use *.conf.  We already have:
> 	pg_hba.conf
> 	pg_ident.conf
> 	pg_service.conf
> 	postgresql.conf
> 	recovery.conf
> If we want an extension on those two files, it seems *.conf 
> is it, and one hopes they would have already configured XP to 
> pull up their favorite editor for *.conf.

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.



pgsql-hackers by date

Next:From: ElayaRaja SDate: 2005-01-10 12:24:28
Subject: unsubscribe
Previous:From: Chris MairDate: 2005-01-10 07:43:59
Subject: Re: PostgreSQL 8.0.0 Release Candidate 4

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2005-01-10 13:19:25
Subject: Re: [BUGS] More SSL questions..
Previous:From: Magnus HaganderDate: 2005-01-10 09:14:02
Subject: Re: RC4 MSI is up...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group