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 1sK0Ie-007oNJ-DC for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 18:44:52 +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 1sK0Ib-004u6K-Pm for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 18:44:50 +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 1sK0Ib-004u5y-Db for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 18:44:50 +0000 Received: from mail-oa1-x2d.google.com ([2001:4860:4864:20::2d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sK0Ia-002W7z-9S for pgsql-general@postgresql.org; Wed, 19 Jun 2024 18:44:49 +0000 Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-2547e1c7bbeso85092fac.2 for ; Wed, 19 Jun 2024 11:44:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718822686; x=1719427486; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ED2jQ+lPVc+wBrh/puf8Y+VLLVsjkDZvSq6nvQIx+7Q=; b=E6DuAyfzrn04qzR7FkphUh8j7fJCNvCHw/mwtRHBbsnEkIC90lZXZf6UdglBfRBn29 wO7fMz0H/kIlSTJfsgGJpNHUxQDNqs4POPrkQQDpRMGzAYhcFBSUvTq9YW50OHDLYhbY Q1w9tgyavz0mTTZyztjiwSIQnXrLSX+tc65jnHklsEcrcPG3JMH2YKtYYpVEKcuruYhR gMl/zWtFGRuAE9QyJgKNFusXwwX1xr9l7aVBKAKihvztwk5p2/7CnIPqAWmvf8AS74kk QlM/PyibOZbnXO+qLtXGYsSOzlCEvnQj82YUWOMOUcak61eLNORwG4E+WyPZ+kmLuBKo DhDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718822686; x=1719427486; h=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=ED2jQ+lPVc+wBrh/puf8Y+VLLVsjkDZvSq6nvQIx+7Q=; b=RJbkooWTuh9wTJp5emxi0ZCyQQKOu5uYMvPpg6EX0a6pg2YFfQH9BXDjdg+DKI1W38 jeaaPmTPdTPIlw5x26lMzBZzKQeUAXIJUB1j893jAW3oaN+HrfBLoqcY1A+a6QM2Ipps MYjmFZNyLP7rAH0x+Kt+Tc/GOcnxFcV+l0u818n3fvH8Hvk+bziFIZZ7ij0zPfBC4abX qNTM/edb5/flUrj5JfHeQUU6doru+E22IlTFsb6BXWbMp69t1zgZmXuY83zhyNY6+Fdx Vb2sm1tn4OQu8Z/5CCaxJd37xKMyVO+er1DSiTuyybtLumBQokYlVod4OQC3liT6XAHC YDSQ== X-Gm-Message-State: AOJu0YzMzASO+B8cq5n7aOztkEe1PEI8efS3Bhht03Oq/Lj616uGsSET YXDixOhtLt/LXXBdidj/vM7kxlLKfULoxv/Kp7WvK2eqqBAJfhqvx0dYAy/aKkobQqqA5ckjoSa o12jLu1G36s93dATGzhKvLEJMEtA6r0GJ X-Google-Smtp-Source: AGHT+IHgqzTJS3mMmty9oa+0ncJPYNSWUlZqt+2bPs/TDlQYnxtNG++p2GTEfU6p5/sxg8PHHNHncHeLLL/vNoEMPME= X-Received: by 2002:a05:6870:b69d:b0:24c:f8dc:2baf with SMTP id 586e51a60fabf-25c94901f68mr3369673fac.10.1718822686514; Wed, 19 Jun 2024 11:44:46 -0700 (PDT) MIME-Version: 1.0 References: <1f1cad79-7e11-5e85-4fe1-e99d5e17d1e@appl-ecosys.com> In-Reply-To: <1f1cad79-7e11-5e85-4fe1-e99d5e17d1e@appl-ecosys.com> From: "David G. Johnston" Date: Wed, 19 Jun 2024 11:44:36 -0700 Message-ID: Subject: Re: Transaction issue To: Rich Shepard Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000a96847061b4297be" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a96847061b4297be Content-Type: text/plain; charset="UTF-8" On Wed, Jun 19, 2024, 11:38 Rich Shepard wrote: > On Wed, 19 Jun 2024, David G. Johnston wrote: > > > Simplest process, after rollback you fix the problem and start again from > > the top of the transaction. > > David, > > That's what I thought I was doing when I re-entered the command to run the > script. That produced the same error because the transaction was not ended. > Then I doubt your claim you sent a rollback command. Or maybe you still have errors in the script. David J. --000000000000a96847061b4297be Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Jun 19, 2024, 11:38 Rich Shepard <rshepard@appl-ecosys.com> wrote= :
On Wed, 19 Jun 2024, David G. Joh= nston wrote:

> Simplest process, after rollback you fix the problem and start again f= rom
> the top of the transaction.

David,

That's what I thought I was doing when I re-entered the command to run = the
script. That produced the same error because the transaction was not ended.=

= Then I doubt your claim you sent a rollback command.=C2=A0 Or maybe you sti= ll have errors in the script.

David J.

--000000000000a96847061b4297be--