Re: LOCK_DEBUG documentation - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: LOCK_DEBUG documentation
Date
Msg-id 200807012149.m61LnDq12091@momjian.us
Whole thread Raw
In response to Re: LOCK_DEBUG documentation  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-patches
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  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] TRUNCATE TABLE with IDENTITY
Next
From: Tom Raney
Date:
Subject: Explain XML patch v2