Re: LOCK_DEBUG documentation

Bruce Momjian <[email protected]>
Newsgroups gmane.comp.db.postgresql.devel.patches
Message-ID <[email protected]>
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> 
> Tom Lane replied:
> >> Documentation patch by Kevin L. McBride explaining LOCK_DEBUG options
> >> in detail.
> 
> > Should this stuff really go into the SGML documentation, when these
> > options will certainly never be enabled anywhere except in developers'
> > private builds?  A few lines of comments in pg_config_manual.h seems
> > a more appropriate solution.
> 
> Call me a traditionalist, but I like all the documentation in one place,
> even if some of it it seldom used. For the record, these options have
> been enabled by myself and others in production systems for debugging
> purposes, and the lack of detail in that section while doing so led to
> the patch. The docs also has the advantage of being more available,
> searchable, and found via the web.

Agreed, applied.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

-- 
Sent via pgsql-patches mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.