Thread: pg_options in postgres 7.3.2
Hi,
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 ...
but I cannot find any output anywhere.
Any helps or tips or “dahs” would be appreciated.
What I’m trying to do is see under my function PL/pgsql function call to see what’s wrong ... what tools do
people use to debug their PL/pgsql. I can’t seem to find very many. Is there a dbms_output equivalent, for instance?
Thanks,
Dick Wieland
I think you want to edit postgresql.conf. --------------------------------------------------------------------------- Dick Wieland wrote: > Hi, > > 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 ... > > but I cannot find any output anywhere. > > Any helps or tips or "dahs" would be appreciated. > > What I'm trying to do is see under my function PL/pgsql function call to > see what's wrong ... what tools do > people use to debug their PL/pgsql. I can't seem to find very many. Is > there a dbms_output equivalent, for instance? > > Thanks, > Dick Wieland > -- 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
"Dick Wieland" <dwieland@bellatlantic.net> 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
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:tgl@sss.pgh.pa.us] Sent: Wednesday, June 18, 2003 5:23 PM To: rwieland@acm.org Cc: pgsql-general@postgresql.org; Dick Wieland@Verizon Subject: Re: [GENERAL] pg_options in postgres 7.3.2 "Dick Wieland" <dwieland@bellatlantic.net> 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