Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
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 Notepad. -- Kevin Brown [EMAIL PROTECTED] ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
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. //Magnus ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
Magnus Hagander [EMAIL PROTECTED] 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 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] 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. I don't think it is bogus. The reason our client config files don't have *.conf is because they have dots --- the leading dot says it is a config file to me. Win32 doesn't support leading dots mean config files so we add *.conf. Also, pg_service.conf is a client file used by libpq. I don't see why file extensions for the server should not also be similar for clients. 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... What I am saying is that no one else uses *.txt for config files on Win32 and it is confusing. The *.txt will confuse everyone, experts and novices, while *.conf is clear but will be a little harder for novices to open. Also remember the files will normally not exist so novices are going to have to create those files first anyway. At this point, Andrew, Magnus, and I who deal with Win32 regularly all feel *.conf is more logical than *.txt. I have not heard anyone say *.txt is better except Tom. Is that enough of a vote? -- 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 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
Bruce Momjian pgman@candle.pha.pa.us writes: At this point, Andrew, Magnus, and I who deal with Win32 regularly all feel *.conf is more logical than *.txt. I have not heard anyone say *.txt is better except Tom. Is that enough of a vote? AFAIR they both said they didn't care; you are the only one who is exercised about this. I don't particularly care either, but I do note that Peter already generated what was supposed to be the final version of the man pages, and we can't change this without changing those. Do what you want; I have more important problems to worry about right now. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
Bruce Momjian wrote: At this point, Andrew, Magnus, and I who deal with Win32 regularly all feel *.conf is more logical than *.txt. I have not heard anyone say *.txt is better except Tom. Is that enough of a vote? *ahem* :-) I though what I said was that we should leave the name alone except for removing a leading dot. I have seen other cases where .foorc became foo.rc on windows, which isn't a bad solution for such files. I honestly don't care that much - it's not worth a religious fight over. cheers andrew ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
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. Currently the two Win32 files with *.txt extensions are: APPDATA/postgresql/pgpass.txt APPDATA/postgresql/psqlrc.txt *.txt was added on Win32 to make them automatically start notepad.exe when clicked on. Here is a copy of the Mozilla directory on XP: [.][..] 1138945.s 1138945.w abook.mab bookmarks-1.html bookmarks-2.html bookmarks-3.html bookmarks-4.html bookmarks-5.html bookmarks-6.html bookmarks.html [Cache][Cache.Trash] cert8.db [chatzilla] [chrome] cookies.txtcookperm.txt downloads.rdf history.dathistory.mabhostperm.1 key3.db localstore.rdf [Mail] mailViews.dat mimeTypes.rdf panacea.datpanels.rdf parent.lockprefs.js search.rdf secmod.db URL.tblXUL.mfl There are no *.txt files even though they are all text files. They are not meant to be edited by hand though. I don't have any *.txt files under \Application Data on my machine. -- 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 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
Bruce Momjian wrote: [.][..] 1138945.s 1138945.w abook.mab bookmarks-1.html bookmarks-2.html bookmarks-3.html bookmarks-4.html bookmarks-5.html bookmarks-6.html bookmarks.html [Cache][Cache.Trash] cert8.db [chatzilla] [chrome] cookies.txtcookperm.txt downloads.rdf history.dathistory.mabhostperm.1 key3.db localstore.rdf [Mail] mailViews.dat mimeTypes.rdf panacea.datpanels.rdf parent.lockprefs.js search.rdf secmod.db URL.tblXUL.mfl There are no *.txt files even though they are all text files. They are Oops, sorry there are two *.txt files for cookies, but most of the configuration files are not *.txt. -- 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 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
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 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] [pgsql-hackers-win32] [BUGS] More SSL questions..
Magnus Hagander [EMAIL PROTECTED] writes: Tom also wrote: Now that I look at it, there are several places that are depending on getenv(HOME) or getenv(USERPROFILE) (on Windows) as the meaning of home directory. In particular ~/.pgpass is sought there, and psql also uses get_home_path in a lot of places. Seems like we should be consistent about this --- either we trust $HOME or we don't. Don't trust $HOME on win32. There is no such thing.It's set by Cygwin, and it's set by the MingW shell, but it's not set by Windows. HOMEDRIVE, HOMEPATH and HOMESHARE are set, but not HOME. You can trust USERPROFILE in NT based OSes. Not sure about 9x. Using the API above is a much nicer way of doing it. We are using $USERPROFILE, not $HOME, on Windows, but I think Magnus is right: we shouldn't be doing that at all. If I don't hear any objections soon, I'm going to replace get_home_path() with code that uses getpwuid (on Unix) or SHGetSpecialFolderPath (on Windows). regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
