Thanks for nailing this down for me. If you're interested in how I stumbled across pg_options ..
In going back, I can see that I was looking at 7.0 documentation ( http://www.postgresql.org/docs/view.php?version=7.0&idoc=0&file=postgres .htm) as downloaded to some user site. I would observe that the 7.0 documents in http://www.postgresql.org/docs/ do not have the version number on their title pages, and while they are clearly listed there as Vx.y.z as they got separated from their labeled links and downloaded onto user sites they lost their version identification. I found the 7.0 documentation for pg_options through a google search for "debugging", and assumed it applied to 7.3.2. Documentation of later versions is clearly marked with the version number, and I can see that there is no mention of pg_options inthe 7.3 documentation. Thanks, Dick Wieland -----Original Message----- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 5:23 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; Dick [EMAIL PROTECTED] Subject: Re: [GENERAL] pg_options in postgres 7.3.2 "Dick Wieland" <[EMAIL PROTECTED]> writes: > I'm wondering if this pg_options "option" works in 7.3.2? I dropped > the following script > verbose=2 > query=4 > hostlookup > showportnumber > as $PGDATA/pg_options and then rehupped with pg_ctl ... There is not, and AFAIR never has been, any such facility as that. Please point out the part of the documentation that confused you into believing this would do something, so we can clarify it. As Bruce noted, $PGDATA/postgresql.conf is the file to be hacking on. regards, tom lane ---------------------------(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
