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 1sK36l-0083wN-Ry for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 21:44:47 +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 1sK36j-0082uB-0K for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 21:44:45 +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 1sK36i-0082kO-L0 for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 21:44:45 +0000 Received: from mail-ot1-x330.google.com ([2607:f8b0:4864:20::330]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sK36h-0028xj-2T for pgsql-general@postgresql.org; Wed, 19 Jun 2024 21:44:44 +0000 Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-6f95be3d4c4so86743a34.3 for ; Wed, 19 Jun 2024 14:44:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718833482; x=1719438282; 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=fL3Xb631TzdLYKdFeBKmgFDX/gjQzRNt3SpBqu3FNZI=; b=U+/IbsFlRznGIprKqdg+ELpxD1tkwngRiDyBcT3xBXJXptk4WW4fqYTW+JM0dtrr01 3IzI+S2YZfOqwdd09m+fZGBmKlqM5VC/I2MO/8YC8Wz4eI7KO5oMUx7uh5c8oYSVsBou Xac+2srNBk7BglouKjBdFi4OyOEqjZnveuVYQix7HNTgSfxyMWyxOLxCHEM+XfR8kf3i Q8HbLDVhAfa0UzfcXDWMli9KjpCvSQEAhrYtnjfHtNYA//3dwKHgNrEEbjFqWKGBY8gQ nAPPqr1xoGv4AM4nPqGI86Gnm8oWjsLc+AIY8TIh2DAagVCw3Q5oZp4sBJ2SG0srXKtb 9xRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718833482; x=1719438282; 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=fL3Xb631TzdLYKdFeBKmgFDX/gjQzRNt3SpBqu3FNZI=; b=P77/ksSMTyjg0Fn9Wq2NXe3rsvJ9KXGyIK9NdIhzOhB6d990vXNkImmP4mMhoVjpZR EGnTR3nc8oYaXO7RanbFPyejkXDjfFAtl8+fXjNKkFtq4IflFY/6NggwAvoIKV5N6TCg hS1HVC8uyOv3U7vHk8GYUgDQrXY+wBN3Lzb7SEa7R2plz7eCF5yYeg/rHmwGACSGhgLx O9mkSYlf4F7dJ5q5yPuYuLqtrQ41fWZK82fGhWQgYtOMz2E8Q4qXao9Hx8F51RrWPzqe NIACPPeaNHDj8PO1d3WBaAqLJVrgf38z7AYo8EYjvVp1fE5ULI5lhUfMk/njqak8YlpC BkuQ== X-Gm-Message-State: AOJu0YwyExIEIC9Mu+e/Qw3mAdXGrwvJvgJsVU91TLfQ+oxwZO7UpR13 CjiezUvgEZJVX3tMWoFzRK66zxqwN1N6DvkLmDf/osMETVlinHl5rsx4ZypA1qd+Mw8JYdG65Gy 05PNL6aCBbOD9pTZatXalxkOosRPRrQ== X-Google-Smtp-Source: AGHT+IH28RhAyiAXPwN/00UL4OYs75pUHY21jyWouzmdpojsC+k+P19UUVxK5Af5NMdFssQ+XZxNHIr5pCJzEwKG1C8= X-Received: by 2002:a05:6870:3325:b0:258:42c8:7f69 with SMTP id 586e51a60fabf-25c949a55e2mr3970194fac.23.1718833482260; Wed, 19 Jun 2024 14:44:42 -0700 (PDT) MIME-Version: 1.0 References: <65F95FD4-CBEA-4E66-AE63-EBC9F617C988@gmail.com> <7678da90-521-3b52-4bb5-11bc9bdf6d1@appl-ecosys.com> <65e3d37-1674-97c9-9010-2196384b851@appl-ecosys.com> In-Reply-To: <65e3d37-1674-97c9-9010-2196384b851@appl-ecosys.com> From: Ron Johnson Date: Wed, 19 Jun 2024 17:44:30 -0400 Message-ID: Subject: Re: Transaction issue To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000002367f7061b451b64" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002367f7061b451b64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 19, 2024 at 5:39=E2=80=AFPM Rich Shepard wrote: > On Wed, 19 Jun 2024, Ron Johnson wrote: > > > The problem is that you don't know where it's failing. > > Ron, > > True that. There's no specificity to why the transaction didn't complete. > > > I suggest you run "\echo all" before running "\i > > insert-law-offices-addr.sql". That way, you'll see which line it barfs > on. > > Good point. I'll do that. In the meantime, commenting out (or removing) t= he > BEGIN; command inserts all rows without error. > > In addition, manually run the "BEGIN;" before the "\i insert-blarge.sql" command. That way, insert-blarge.sql just inserts. My reasoning: since you control the ROLLBACK, you should also control the BEGIN. --0000000000002367f7061b451b64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jun 19, 2024 at 5:39=E2=80=AFPM R= ich Shepard <rshepard@appl-e= cosys.com> wrote:
On Wed, 19 Jun 2024, Ron Johnson wrote:=

> The problem is that you don't know where it's failing.

Ron,

True that. There's no specificity to why the transaction didn't com= plete.

> I suggest you run "\echo all"=C2=A0 before running "\i<= br> > insert-law-offices-addr.sql".=C2=A0 That way, you'll see whic= h line it barfs on.

Good point. I'll do that. In the meantime, commenting out (or removing)= the
BEGIN; command inserts all rows without error.

In addition, manually run the "BEGIN;" before the &qu= ot;\i insert-blarge.sql" command.

That way, i= nsert-blarge.sql just inserts.=C2=A0 My reasoning: since you control the RO= LLBACK, you should also control the BEGIN.

--0000000000002367f7061b451b64--