Re: GUC and postgresql.conf docs
От | Bruce Momjian |
---|---|
Тема | Re: GUC and postgresql.conf docs |
Дата | |
Msg-id | 200305150337.h4F3b5A03611@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: GUC and postgresql.conf docs (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Tom Lane wrote: > Josh Berkus <josh@agliodbs.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@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
В списке pgsql-hackers по дате отправления: