pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: troy@frericks.us
Subject: How to reference the type of lock in the documentation.
Date: Wed, 29 Jun 2022 20:45:11 +0000
Message-ID: <165653551130.665.8240515669521441325@wrigleys.postgresql.org> (raw)

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/explicit-locking.html
Description:

On page https://www.postgresql.org/docs/10/explicit-locking.html, I'd like
to suggest a search-engine-optimization improvement. Generally, but
especially on this page, it'd be nice to have the lock name along with the
user-friendly name. For example, with the first use of "SHARE UPDATE
EXCLUSIVE", I'd like to see the lock name with it, for example, "SHARE
UPDATE EXCLUSIVE (ShareUpdateExclusiveLock)". 
Troy.
#


view thread (5+ messages)  latest in thread

Message-ID: <165653551130.665.8240515669521441325@wrigleys.postgresql.org>
Permalink:  ../165653551130.665.8240515669521441325@wrigleys.postgresql.org/
Also on:    postgresql.org/message-id/165653551130.665.8240515669521441325@wrigleys.postgresql.org

 · 

reply

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: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, troy@frericks.us
  Subject: Re: How to reference the type of lock in the documentation.
  In-Reply-To: <165653551130.665.8240515669521441325@wrigleys.postgresql.org>

* 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