Re: LOCK_DEBUG documentation

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Subject: Re: LOCK_DEBUG documentation
Date: 2008-05-27 14:16:18
Message-ID: 52caad80067db7e970d9585f10fee9f0@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


-----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(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200805271012
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Henry Combrinck 2008-05-27 15:13:26 BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code
Previous Message David Fetter 2008-05-26 22:02:59 Re: Updated patch (Re: [PATCHES] WITH RECURSIVE patch V0.1)