From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: GUC and postgresql.conf docs |
Date: | 2003-05-15 03:37:05 |
Message-ID: | 200305150337.h4F3b5A03611@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > GUC Options with no documentation:
> > The following options exist in postgresql.conf.sample and in guc.c but not in
> > the online documenation anywhere the search box can find:
>
> > trace_locks
> > trace_userlocks
> > trace_lwlocks
> > debug_deadlocks
> > trace_lock_oidmin
> > trace_lock_table
> > show_btree_build_stats
>
> These are all debugging options that probably don't need to be in the
> user documentation (ie, if you aren't familiar enough with the source
> code to find out about 'em from there, you do not need them and should
> probably not be messing with 'em --- in fact, many of them don't even
> exist except in specially-hacked builds). I'd vote for taking them out
> of postgresql.conf.sample, I think.
Agreed, they should not be in postgresql.conf.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-05-15 03:38:34 | Re: GUC and postgresql.conf docs |
Previous Message | Tom Lane | 2003-05-15 03:24:42 | Re: SET CONSTRAINTS not schema-aware |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-05-15 03:38:34 | Re: GUC and postgresql.conf docs |
Previous Message | george young | 2003-05-14 19:24:32 | pygresql build/install problems: use setup.py? |