pgsql: Change locktype "speculative token" to "spectoken".

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Change locktype "speculative token" to "spectoken".
Date: 2020-05-16 01:48:00
Message-ID: E1jZlvk-0002Dr-LS@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Change locktype "speculative token" to "spectoken".

It's just weird that this name wasn't chosen to look like an
identifier. The suspicion that it wasn't thought about too
hard is reinforced by the fact that it wasn't documented in
the pg_locks view (until I did so, a day or two back).

Update, and add a comment reminding future adjusters of this
array to fix the docs too.

Do some desultory wordsmithing on various entries in the wait
events tables.

Discussion: https://postgr.es/m/24595.1589326879@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/474e7da6485687425d216eda1685d7e530b24fd6

Modified Files
--------------
doc/src/sgml/catalogs.sgml | 2 +-
doc/src/sgml/monitoring.sgml | 93 +++++++++++-----------
src/backend/utils/adt/lockfuncs.c | 7 +-
.../expected/insert-conflict-specconflict.out | 10 +--
.../specs/insert-conflict-specconflict.spec | 2 +-
5 files changed, 58 insertions(+), 56 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2020-05-16 09:19:28 pgsql: Fix assertion with relation using REPLICA IDENTITY FULL in subsc
Previous Message Alvaro Herrera 2020-05-16 00:02:19 pgsql: Fix walsender error cleanup code