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 1sK2NZ-0080ZF-Ce for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 20:58:05 +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 1sK2NW-0072eu-Tj for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 20:58:03 +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.94.2) (envelope-from ) id 1sK2NW-0072ed-Iz for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 20:58:03 +0000 Received: from mail-oa1-x33.google.com ([2001:4860:4864:20::33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sK2NV-0028d7-3s for pgsql-general@postgresql.org; Wed, 19 Jun 2024 20:58:02 +0000 Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-25cb3f1765bso156009fac.1 for ; Wed, 19 Jun 2024 13:58:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718830680; x=1719435480; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=GON65SJsv01lSn+MuZeFxLK7RfY+MW1EaNe0RkAeqrY=; b=KQtyV0zflqoPavgqvCEGoZtEoi8UsvLdWXdQ4a3TFf0gDrmNoyZGVz6TappaA7ZqRb HmaDgSv1TMT2c5LaMIFXmlXnraWBOHSBxqt8+QX8cX1RAjeQ96F/sDlAwwAyvMyWz6ar M3zEVkOTRDWb5d0RryFMG/8f+aEECtjvjQG5tXuLQEDl9WVb8TWQtYcozk9+4I/omuyT sEYQspas38uYRUQDghpLMj24WfvSNiAv7GMBFgwp75Y3tDuC/FYFoCH1rwDC5yXDbaeg T48fviGANgjzU2ThTcv7ADsfDDjVtvDSdNBjxZEaEJqOn+GYoF8AJ4z7kLEwLXKwD7cs rwzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718830680; x=1719435480; h=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=GON65SJsv01lSn+MuZeFxLK7RfY+MW1EaNe0RkAeqrY=; b=QH4EWMV6DPwD6lerAdvWC9G/vsMpOT3GogAZt/ZXElJ0Ns4ZCwKzL4Acm35ImL0p8r E8/k/pUEhlsxFH/P5YjvagXB+SAB2BpEFa23hnC/h75gtpydRRh/XUPKkqRi1iqfTyBK flm7K7uCPgUM26L6fe5U3GyRp23H0cnw+a+aUiOckCKeNVTuNfQqFwZpXrZkHwvtg6r+ xA1s51ejGEi8n7/1N/hZt5tQYRrhREhWHVdDI92zJYpGTu3Txe7I8GScFfXUMzTkA6pX /ks4h+qlGaS57u+rRoqbf7+jPxiw95mr+dvFxbe1nboKOEz10BELzkFDwI+L/Fd+uHlj EqnQ== X-Gm-Message-State: AOJu0Yw+wyjN1b32gP8oTZmnq3602Q4+pN2qKJ2jiuDALyz9HvkUjxO7 CO8jaWG6M8c7cQMa+bclGlo3/qBdKxfF0iP/ZFMDoADOR3KNNy0p1yBN2E3Wbo4yWuGTRjcFSLG AvxSK21NArcb00cMhZ93VY0xsFLS3f7tU X-Google-Smtp-Source: AGHT+IF/6ejl/ePvplPOs6VRbswBgDdJPHR1orNNezltHOjbllTyRi8PPRsF97YqNPyrV74WmgYWit2KOm/tV9sj780= X-Received: by 2002:a05:6870:63a4:b0:255:c21d:a9db with SMTP id 586e51a60fabf-25c948f4129mr4163365fac.1.1718830679892; Wed, 19 Jun 2024 13:57:59 -0700 (PDT) MIME-Version: 1.0 References: <65F95FD4-CBEA-4E66-AE63-EBC9F617C988@gmail.com> <7678da90-521-3b52-4bb5-11bc9bdf6d1@appl-ecosys.com> In-Reply-To: <7678da90-521-3b52-4bb5-11bc9bdf6d1@appl-ecosys.com> From: Ron Johnson Date: Wed, 19 Jun 2024 16:57:48 -0400 Message-ID: Subject: Re: Transaction issue To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000001aaa27061b447438" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001aaa27061b447438 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 19, 2024 at 4:33=E2=80=AFPM Rich Shepard wrote: > On Wed, 19 Jun 2024, Alban Hertroys wrote: > > > The error prior to those statements is what you need to look at. That= =E2=80=99s > > what=E2=80=99s causing the transaction to fail. > > Alban/Adrian, > > > I get the impression that you=E2=80=99re executing shell scripts that r= un the > psql > > command-line utility. > > That's what I do as I've not taken the time to finish the GUI with TKinte= r. > > Here's the latest example: > bustrac=3D# \i insert-law-offices-addr.sql > psql:insert-law-offices-addr.sql:1: ERROR: current transaction is > aborted, commands ignored until end of transaction block > psql:insert-law-offices-addr.sql:69: ERROR: current transaction is > aborted, commands ignored until end of transaction block > > Line 1 is the BEGIN; statement; line 69 is the last row of data to be > inserted. > The problem is that you don't know where it's failing. I suggest you run "\echo all" before running "\i insert-law-offices-addr.sql". That way, you'll see which line it barfs on. --0000000000001aaa27061b447438 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jun 19, 2024 at 4:33=E2=80=AFPM R= ich Shepard <rshepard@appl-e= cosys.com> wrote:
On Wed, 19 Jun 2024, Alban Hertroys wro= te:

> The error prior to those statements is what you need to look at. That= =E2=80=99s
> what=E2=80=99s causing the transaction to fail.

Alban/Adrian,

> I get the impression that you=E2=80=99re executing shell scripts that = run the psql
> command-line utility.

That's what I do as I've not taken the time to finish the GUI with = TKinter.

Here's the latest example:
bustrac=3D# \i insert-law-offices-addr.sql
psql:insert-law-offices-addr.sql:1: ERROR:=C2=A0 current transaction is abo= rted, commands ignored until end of transaction block
psql:insert-law-offices-addr.sql:69: ERROR:=C2=A0 current transaction is ab= orted, commands ignored until end of transaction block

Line 1 is the BEGIN; statement; line 69 is the last row of data to be
inserted.

The problem is that you don't know whe= re it's failing.

I suggest you run "\echo all"=C2=A0 before running "\i insert-law-offices-addr.sql".=C2=A0 That= way, you'll see which line it barfs on.
--0000000000001aaa27061b447438--