Bruce Momjian wrote:
> Magnus Hagander wrote:
> > >> My feeling is that the *.txt is actually misleading because
> > >people will
> > >> think of it as a file full of freeform text (paragraphs) and not a
> > >> configuration file.
> > >
> > >Why would they think that? If notepad tends to auto-wrap files then
> > >this argument has some force; I'm not very familar with it though.
> >
> > It does not. There is an option to make it *show* the file with wrapped
> > line, but it does not even have the capability to wordwrap the files
> > themselves.
> >
> > 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. 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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073