From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Wrong advisory locks docs in pg_locks
Date: Sat, 26 Nov 2011 12:17:27 -0500
Message-ID: <13976.1322327847@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+mi_8Z67=OTJrNMxzKvtsTRcKXmrN50GUjtnLvkZ3=d2-ky1g@mail.gmail.com>
References: <CA+mi_8Z67=OTJrNMxzKvtsTRcKXmrN50GUjtnLvkZ3=d2-ky1g@mail.gmail.com>
Daniele Varrazzo <daniele.varrazzo@gmail.com> writes:
> documentation about advisory locks in the pg_locks view
> <http://developer.postgresql.org/pgdocs/postgres/view-pg-locks.html;
> is incorrect/incomplete: the space specifier field is objsubid, not
> objid, and there is no information about how the key is stored.
Actually, there is a paragraph further down that correctly explains what
advisory locks look like. I think the best fix is to remove the
incorrect annotation on objid and leave it at that; shoehorning
additional sentences into table columns that are meant to contain
short phrases is not an improvement.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, daniele.varrazzo@gmail.com
Subject: Re: Wrong advisory locks docs in pg_locks
In-Reply-To: <13976.1322327847@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox