Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFDvI-0001Ba-7D for pgsql-committers@arkaria.postgresql.org; Tue, 10 Jan 2023 12:40:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pFDvG-0005w2-UR for pgsql-committers@arkaria.postgresql.org; Tue, 10 Jan 2023 12:40:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFDvG-0005vY-Ll for pgsql-committers@lists.postgresql.org; Tue, 10 Jan 2023 12:40:10 +0000 Received: from ewsoutbound.kpnmail.nl ([195.121.94.170]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFDvC-00081r-Rl for pgsql-committers@lists.postgresql.org; Tue, 10 Jan 2023 12:40:09 +0000 X-KPN-MessageId: e2c1807a-90e3-11ed-a286-005056ab378f Received: from smtp.kpnmail.nl (unknown [10.31.155.37]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id e2c1807a-90e3-11ed-a286-005056ab378f; Tue, 10 Jan 2023 13:39:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=xs4all01; h=content-type:from:to:subject:mime-version:date:message-id; bh=WmFCLRPzvqy2QGd/Re0NapK9ZRFNAFxKAJKHMmgAo2Y=; b=ller4LhiNOldGQmRQI4ZG/AH+zu80wCgRV1PoBRTF7x23clDchAGxQvf+SMuGkHC0v5yyW8zoRez5 9Ddrm7wyACj5LifDhIgrJSC3hAVWyi+aJKkoFc3HaXEUDL9TjPrccU6y+DWMCpQDttz8GSqkYvU6jn yuBqYJ0rRrtwg/9yNbztfeaRZQmuZ+c2St78m5YDo0KAr6P8gdNhJMq6gP4eE3PkDypJXrPSo7jOdt EtreCiVrcSCXXZgcuAhX/yUpA/eirRyfXLtJuoNZ38xqI6vGyCodLhsAKrb7dJx9hzpzL8QXnu4rTY LwvKki0o3ViowI/Ktf6piTT91Iq2YMg== X-KPN-MID: 33|K90iIxGTYimvVs+7gSr9cbn1+O6dg0kKH5eng8cfK3giUBl36exB5Q4FhnV5bQs Nkt7XMnfPEH36vvusWTZdQM+5Ym2b1NepEBXjTWRvUoA= X-KPN-VerifiedSender: Yes X-CMASSUN: 33|8WqbJ+j1R7JUwp7+Q1f0YwN2BGbBqRzaGCLbi/4ePDAz1U4mLi+u/L3Ew9+7lm/ IVgyughUApJzp9hA89HzKQQ== X-Originating-IP: 82.151.32.184 Received: from [192.168.178.25] (unknown [82.151.32.184]) by smtp.xs4all.nl (Halon) with ESMTPSA id e755ed64-90e3-11ed-ae06-005056ab1411; Tue, 10 Jan 2023 13:40:03 +0100 (CET) Message-ID: Date: Tue, 10 Jan 2023 13:40:03 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: pgsql: Fix the display of lock information for specktoken. Content-Language: en-US To: Amit Kapila , pgsql-committers@lists.postgresql.org References: From: Erik Rijkers In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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(+) >