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 1sJzin-007joN-9J for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 18:07:49 +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 1sJzil-004AdE-1Q for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 18:07:47 +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 1sJzik-004Ad3-Mj for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 18:07:47 +0000 Received: from mail-oa1-x29.google.com ([2001:4860:4864:20::29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJzij-002Vqa-EJ for pgsql-general@postgresql.org; Wed, 19 Jun 2024 18:07:46 +0000 Received: by mail-oa1-x29.google.com with SMTP id 586e51a60fabf-25982aa59efso62618fac.3 for ; Wed, 19 Jun 2024 11:07:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718820463; x=1719425263; 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=j/ma7ltbBBMb3QG5yO74p9dbIGZs52rfzQ6qnLLyysk=; b=hxB9mg8TjLACC5kVReH7bdUEwadAKCF/dFPsWBNoqmURdYf0UwALBmBnrrgnrZUw6h bTNnn1ZVq9MGwnqTWNcQDwtP3NKxHWKOapbtx5Lz0zpw+/ry48+Q1UTk8qgQRMzu3R3Z 48PrGn3e9cx7Hb5lFPvm3IXTzCa2sZV1U3LmZy8fCAA8xOjcyIID5ppJlsWZi+Hp9XK/ FeReXYklZpilLSWldn73VgCks4JUeMjCDX5X31J2BsXUobd4AYJzBv1TFxf0XBSVFfgR yi+34HQx4oqcDam3mdG9ZQg0xMIjGkesMD8SYDPwfUYHOIpUVCoR/eTOANCYNOdC3Zjd +kVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718820463; x=1719425263; 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=j/ma7ltbBBMb3QG5yO74p9dbIGZs52rfzQ6qnLLyysk=; b=dsMrBgBVBaM3oDWCIYoDQciQiu4G7BgMin8aGrdvUzvqYH7csEZC/zKn35jFwJxNEK i2HOF/HyQa18oyQFQ8G89yLPwi/BoogdOylsAo1wbl8utVjAsUI9qxL5FkDF5bv0Hzkv iu5QoLx4xZ7UKFVVtHHEa6KmYPD7LQjzFDjpA0qzuH3G1i62wj6cMoRsSMjtbZWwbH0v xmUqK1ZHDEdaSyoUrLEc29qtSf9/yhYu05BSXuTQpHIrwEl1pAZUNmHXIJhYg29A0GFu sHFyC8PPe86kKKc82xyrOiS60wcXr3jmE7OrTnN/gsfPuZAX8ze9NWPf3VXsbibhgLtc nvGg== X-Gm-Message-State: AOJu0YylcFYxD0o9Y3yqC3pEaOXiNC3FklRYvExc5vJXAL5LnIZ2rTWs jsEca5PRP+5QQec7i+HTPvzxzzt+slZ5V3mCLkIS0FQIisG9jwz3KJxdhR9Y3/+/SkqBmSXQBpK Qx3lupLoZI9uC+iEwgZFOn2z1udTMJw== X-Google-Smtp-Source: AGHT+IH+uek0lwmIhbFiTdpdmqOz8fWK/mHsYO0F7CWx9AXqzyFzQZL6xaN3gMHbS48QMNX5Ix99Uq5Y10FkXgtQiys= X-Received: by 2002:a05:6870:1705:b0:254:c842:46f0 with SMTP id 586e51a60fabf-25c94d7b65cmr3210309fac.59.1718820463460; Wed, 19 Jun 2024 11:07:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Wed, 19 Jun 2024 11:07:06 -0700 Message-ID: Subject: Re: Transaction issue To: Rich Shepard Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000028469d061b42135f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000028469d061b42135f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 19, 2024 at 10:56=E2=80=AFAM Rich Shepard wrote: > I now insert rows using a transaction. Sometimes psql halts with an error= : > ERROR: current transaction is aborted, commands ignored until end of > transaction block > > I issue a rollback; command but cannot continue processing. What is the > appropriate way to respond to that error after fixing the syntax error? > Simplest process, after rollback you fix the problem and start again from the top of the transaction. David J. --00000000000028469d061b42135f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jun 19, 2024 at 10:56=E2=80=AFAM Rich Shepard <= rshepard@appl-ecosys.com>= ; wrote:
I now insert rows using a transaction. Som= etimes psql halts with an error:
ERROR:=C2=A0 current transaction is aborted, commands ignored until end of = transaction block

I issue a rollback; command but cannot continue processing. What is the
appropriate way to respond to that error after fixing the syntax error?

Simplest process, after rollbac= k you fix the problem and start again from the top of the transaction.

David J.

--00000000000028469d061b42135f--