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

From Amit Kapila
Subject Re: pgsql: Fix the display of lock information for specktoken.
Date
Msg-id CAA4eK1L2sCqQyjTadnpUeEx-OXi3vf6hm+SCmTgF-oE8wo5_2A@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Fix the display of lock information for specktoken.  (Erik Rijkers <er@xs4all.nl>)
List pgsql-committers
On Tue, Jan 10, 2023 at 6:10 PM Erik Rijkers <er@xs4all.nl> wrote:
>
> 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'
>

Thanks for the report. Justin has already reported this [1] and it
seems Michael is planning to deal with this along with other typos.

[1] - https://www.postgresql.org/message-id/20230110045722.GD9837%40telsasoft.com

-- 
With Regards,
Amit Kapila.



pgsql-committers by date:

Previous
From: Dean Rasheed
Date:
Subject: pgsql: Fix MERGE's test for unreachable WHEN clauses.
Next
From: Robert Haas
Date:
Subject: pgsql: Restrict the privileges of CREATEROLE users.