Thread: LOCK_DEBUG documentation

Documentation patch by Kevin L. McBride explaining LOCK_DEBUG options
in detail.

--
Greg Sabino Mullane
End Point Corporation

Greg Sabino Mullane <greg@turnstep.com> writes:
> 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.

            regards, tom lane

-----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.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200805271012
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkg8F04ACgkQvJuQZxSWSsjNiQCffXM6m8N6DGW9fP3LmVvIGMDo
Y30AoJ0fD2G0n1j5g1HdOukFWppd8jgu
=6tFr
-----END PGP SIGNATURE-----

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. +