Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vqJ2C-008SV8-1g for pgsql-general@arkaria.postgresql.org; Wed, 11 Feb 2026 22:50:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vqJ2B-006JOf-28 for pgsql-general@arkaria.postgresql.org; Wed, 11 Feb 2026 22:50:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vqJ2B-006JOW-17 for pgsql-general@lists.postgresql.org; Wed, 11 Feb 2026 22:50:12 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vqJ29-00000000C3E-2k7V for pgsql-general@postgresql.org; Wed, 11 Feb 2026 22:50:11 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 61BMnv95101917; Wed, 11 Feb 2026 17:49:57 -0500 From: Tom Lane To: Nico Heller cc: pgsql-general@postgresql.org Subject: Re: Guarantee order of batched pg_advisory_xact_lock In-reply-to: References: <93fb937f-9f4d-4bd7-b7e6-51d5f98859d9@posteo.de> <14506.1770844674@sss.pgh.pa.us> Comments: In-reply-to Nico Heller message dated "Wed, 11 Feb 2026 21:51:40 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <101915.1770850197.1@sss.pgh.pa.us> Date: Wed, 11 Feb 2026 17:49:57 -0500 Message-ID: <101916.1770850197@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nico Heller writes: > So it would probably be better to ORDER BY the hashtextended result > instead of :keysToLock, right? Yeah, that seems like it'd work, if you have no other dependencies on the locking order. regards, tom lane