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 1sWtKN-000Imc-Eb for pgsql-general@arkaria.postgresql.org; Thu, 25 Jul 2024 07:55:55 +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 1sWtKL-00CX3g-0z for pgsql-general@arkaria.postgresql.org; Thu, 25 Jul 2024 07:55:53 +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 1sWtKK-00CX1a-M0 for pgsql-general@lists.postgresql.org; Thu, 25 Jul 2024 07:55:52 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sWtKF-001MVC-1Q for pgsql-general@lists.postgresql.org; Thu, 25 Jul 2024 07:55:52 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-2642cfb2f6aso320544fac.2 for ; Thu, 25 Jul 2024 00:55:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721894145; x=1722498945; 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=8+U9C9cDAwxFZ+KKp/wQ3oziQ1Ls9mVvu0zNDea2lWk=; b=QPfBtlvVmcP9b1o7ZXaQ4UEFSmxhUR3P5kbDSyVWFDV/pK+2Kq0XZe1KUgCXiF/NH7 aV6ZDmmysacj2RimWQV/R9KO7NcSUZJeQH/0nTXQGaJspuu5/+1orJyU4wguIf3PJDyg A4dorzQb8/OjTkxF3UN8oi0mGL6SZmZMdnlMJIiHNHq2G38CWc9viqsQNKOlmzy+4bb/ aq6sBPO25vQmqvyrJCRLP+CHH6LAx5whSrJtc6FFk066f8ljRivaBt7LvJ/jFc5+H0ap eypmxxCvI2AGkcu0w/pXqA/WDdpkIeSnxsbujW1ymQ9zmXDcm5PBE9tkfLYlSlrHP1K3 Uzlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721894145; x=1722498945; 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=8+U9C9cDAwxFZ+KKp/wQ3oziQ1Ls9mVvu0zNDea2lWk=; b=ABBenzOmBFBoqTbAl4fzL6H3/vPFn19LHp799SSae/eM+ASF9y+m5SRpE2mY4X4G7w IgSXy3loOTDXFa0VSku3mFS4a5AKJgJnygduDRKccNJxXi+Fy3cJxoTrmYh4TcUdDOqu A71d7CXnfGirXJ3+UJb5vWZG0lFhDZZywwBuS0PkJKba0Ix2bx7E4wgp6pp6llhgwQHQ c9ZpqksQM+c5FbPRx5WQVrwJKllKPunVe9ssaV0B/dYucK2y8udLQO9JSes0j0Oe7w8f Dms01U9KJjEudY4WPXblyCtcqC7QmdvJeQrKJuBx37qYUxKbJaBsNSyJaqvOZLsO7nxI 4XKw== X-Forwarded-Encrypted: i=1; AJvYcCUJGYks1UYtTSpxlRJcHDTAQsBGm5RWv6KZZsbKxvl3ZfPGfJOWZ4sVosSNKmRjkBBs3XPd0z5c/wkuw6GyTKys9DlhCEI29kocXtQktYPr3HVo X-Gm-Message-State: AOJu0YxW2zjxRjM4COjaY8XyXouTkAULA15Nva8R+kuhQrxQK//n8kOg c2Ksu1j/zJi9dhrmblpPQxjxqpgG/22Z1kptDBvDmkXSUG+sdzJ9gtNMjdOZIXBVe9owb4tvZP9 lyhU7BJe2baCMF/QE89tvuMvJhoo= X-Google-Smtp-Source: AGHT+IFph7G5cAm1zV5FjwDQEwLBJfPlQ/j18ee0xrBb5v6d1xcvDO/tcQ0D1XpXG3ufOuhD2+8Id+KN8Lq3YlLJRR0= X-Received: by 2002:a05:6870:7185:b0:260:e83b:cc13 with SMTP id 586e51a60fabf-266cc3aa278mr1284917fac.28.1721894145231; Thu, 25 Jul 2024 00:55:45 -0700 (PDT) MIME-Version: 1.0 References: <1085896.1721766747@sss.pgh.pa.us> In-Reply-To: From: Dominique Devienne Date: Thu, 25 Jul 2024 09:55:33 +0200 Message-ID: Subject: Re: Issue while creating index dynamically To: veem v Cc: Tom Lane , Ron Johnson , pgsql-general 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 Thu, Jul 25, 2024 at 7:42=E2=80=AFAM veem v wrote: > I was thinking the individual statement will work fine if I pull out thos= e from the begin..end block, as those will then be not bounded by any outer= transaction. > However, When I was trying it from dbeaver by extracting individual inde= x creation statements rather from within the "begin ..end;" block, it still= failed with a different error as below. Why is it so? > > "SQL Error [25001]: Error: create index concurrently cannot be executed = within a pipeline " Perhaps it's an artifact of DBeaver using [LibPQ's pipeline mode][1] when executing scripts? Maybe give it a try in `psql` instead. Or find a setting to disable pipeline mode? (which is new to v14). [1]: https://www.postgresql.org/docs/current/libpq-pipeline-mode.html