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.94.2) (envelope-from ) id 1tDqYS-003aNn-Ba for pgsql-general@arkaria.postgresql.org; Wed, 20 Nov 2024 19:40:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tDqYQ-008cJV-O0 for pgsql-general@arkaria.postgresql.org; Wed, 20 Nov 2024 19:39:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDqYQ-008cJL-9W for pgsql-general@lists.postgresql.org; Wed, 20 Nov 2024 19:39:58 +0000 Received: from mail-lf1-x135.google.com ([2a00:1450:4864:20::135]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tDqYO-002yVV-3I for pgsql-general@lists.postgresql.org; Wed, 20 Nov 2024 19:39:57 +0000 Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-53d9ff92edaso117005e87.1 for ; Wed, 20 Nov 2024 11:39:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732131595; x=1732736395; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=dzasi0RMIeyEoEMnHhx35tP7HQ0JM3mq9oIGVy59whU=; b=Z/kg1KTGTp2OK2j+mZePjUgsswutW/E3ohc6K/nsqWjLWe7rFbWMJcdchID/yvkren /qTFWi3r7uyJclQPLjOXpKxJpEulKczq7iv4vNQ2t0s2m8FNneNt3IdjscLVFKCmdkZt wM48lp8I2IG5jvwxD2Oj0f2zuAJDmPOKLzdnVRKkOvN6RlB1P4vus/Zv0VkGUJEsfydG 49zTb4YpMKO5cJvUQmjwTb5GMt4ntQVQyUh9zA29/8lYW8dDE61wIgIqtt/l60sF5rll hp6y1SMiZPnQfdNh790HKhx8YC/fOuUNmcZCZ7qQoG/Mr0K4BhG5D8mL3ZVVQ4aDx7u/ nFLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732131595; x=1732736395; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=dzasi0RMIeyEoEMnHhx35tP7HQ0JM3mq9oIGVy59whU=; b=xIEik7XY0mQ625wZcxP4JpnI83D+hxHw+kIWP6yRWz4ekFlZOt8lka2YUcLCbt8xNQ ahgSFeSYGFHH21BBp+T78ESjmRnYZV3UtkqLZTOnfh62fvNr+jcpJV9MdTZpLlC0TxcZ zhgbPCHo3dBcQdCHcWnMqooeK/D3hurUV9HxUSzkzXYANaQCE3Y+u2Ggux4923clHdw1 gwLGoHWMikQN2pqvw/mccby2+OgtMOB2AwQLMr7iuVwUhLIJaMD8epBuSfwns2kdGRQd t/l4EOE7EOskMB9NcaQkuTh27YE7krb2hTxRTmT4eva3ZRzKeyOL1k5CHnTO1mF/RhcN P64g== X-Gm-Message-State: AOJu0YwjE6QzzY4G6ELggJFNLIlVmZY1OhNo/fUBFgLg7ov6TDXVbQUm 7sd2E9Ub6QPe7PI/mfrym1imzsoZ9rSE9QqFcYWcCpG2hFNQbqPzw8wFPmnbNRg55wbB9bV2hCL CuoH/R/8CVBX2PhEoYBSOxXxoPng91wvo X-Google-Smtp-Source: AGHT+IG+9y4AWkcUo+jecGtoYmNB5U/i7ZCKawBpJyZTclzYHDx0IW4Di38MJ+qbEwPcbZOir9MAZA4d4SZWhj+pWlY= X-Received: by 2002:a05:6512:23aa:b0:537:a745:3e with SMTP id 2adb3069b0e04-53dc136a9bfmr1935094e87.45.1732131594630; Wed, 20 Nov 2024 11:39:54 -0800 (PST) MIME-Version: 1.0 References: <232551.1732129077@sss.pgh.pa.us> In-Reply-To: <232551.1732129077@sss.pgh.pa.us> From: Istvan Soos Date: Wed, 20 Nov 2024 20:39:44 +0100 Message-ID: Subject: Re: A table lock inside a transaction depends on query protocol being used? To: Tom Lane Cc: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Nov 20, 2024 at 7:57=E2=80=AFPM Tom Lane wrote: > but I wonder if you could be failing to close out the SELECT statement be= fore issuing ALTER. Thanks! This led me to check some debug details, and in fact we don't close the portal, only the statement. (Besides a bug in the debug log...) Now I know what to fix :). Thanks, Istvan