Re: pgsql: Fix the display of lock information for specktoken. - Mailing list pgsql-committers

From Erik Rijkers
Subject Re: pgsql: Fix the display of lock information for specktoken.
Date
Msg-id bb2b3f5a-98cf-5f46-44cb-6a63ffc581b0@xs4all.nl
Whole thread Raw
In response to pgsql: Fix the display of lock information for specktoken.  (Amit Kapila <akapila@postgresql.org>)
Responses Re: pgsql: Fix the display of lock information for specktoken.  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-committers
On 1/10/23 04:34, Amit Kapila wrote:
> Fix the display of lock information for specktoken.
> 
> A transaction id is now displayed in the transactionid field and
> speculative insertion token is displayed in the objid field.

Hi,

'A specualtive insertion lock'  should be
'A speculative insertion lock'

Erik

> Author: Sawada Masahiko
> Reviewed-by: Amit Kapila
> Discussion: https://postgr.es/m/CAD21AoCEKxZztULP1CDm45aSNNR1QO-Bh1q6LMTspQ78PBuJrw@mail.gmail.com
> 
> Branch
> ------
> master
> 
> Details
> -------
> https://git.postgresql.org/pg/commitdiff/f745739697e49a38a31a755d7d36d6c97008dd9f
> 
> Modified Files
> --------------
> doc/src/sgml/system-views.sgml    |  6 ++++++
> src/backend/utils/adt/lockfuncs.c | 12 ++++++++++++
> 2 files changed, 18 insertions(+)
> 



pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: New header varatt.h split off from postgres.h
Next
From: Dean Rasheed
Date:
Subject: pgsql: Fix MERGE's test for unreachable WHEN clauses.