| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | Amit Kapila <akapila(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Fix the display of lock information for specktoken. |
| Date: | 2023-01-10 15:22:05 |
| Message-ID: | CAA4eK1L2sCqQyjTadnpUeEx-OXi3vf6hm+SCmTgF-oE8wo5_2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Tue, Jan 10, 2023 at 6:10 PM Erik Rijkers <er(at)xs4all(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-01-10 17:44:35 | pgsql: Restrict the privileges of CREATEROLE users. |
| Previous Message | Dean Rasheed | 2023-01-10 14:20:27 | pgsql: Fix MERGE's test for unreachable WHEN clauses. |