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

Re: [pgsql-hackers-win32] [BUGS] More SSL questions..

From: Kevin Brown <kevin(at)sysexperts(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [pgsql-hackers-win32] [BUGS] More SSL questions..
Date: 2005-01-13 13:03:54
Message-ID: 20050113130353.GA22586@filer (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-hackers-win32
Bruce Momjian wrote:
> > > FWIW, I've seen several apps that use .txt for config files, but I can't
> > > think of an example right now. Most don't though - .cfg or .conf is
> > > probably most common. Except for the majority of windows programs that
> > > don't use config files - they use the registry. But I see no reason *at
> > > all* for us to want to do that :-) It also more or less requires you to
> > > write a GUI to change the config stuff and in that case the file
> > > extension becomes irrelevant.
> > 
> > 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.

For what it's worth, I always thought that text configuration files on
Windows platforms generally used the '.ini' extension.  I believe on
most Windows systems that extension is by default associated with

Kevin Brown					      kevin(at)sysexperts(dot)com

In response to


pgsql-hackers by date

Next:From: Greg StarkDate: 2005-01-13 13:59:31
Subject: Re: [HACKERS] Much Ado About COUNT(*)
Previous:From: David GaramondDate: 2005-01-13 11:34:30
Subject: Re: [HACKERS] Much Ado About COUNT(*)

pgsql-hackers-win32 by date

Next:From: Merlin MoncureDate: 2005-01-13 15:40:03
Subject: Re: [BUGS] psql: no chance to enter password in certain situations
Previous:From: Együd CsabaDate: 2005-01-13 12:33:16
Subject: pgsqlODBC problems

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