From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Transaction issue |
Date: | 2024-06-19 20:43:48 |
Message-ID: | bfcc535f-403c-4ce4-b096-c93da5b0f1b6@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/19/24 13:33, 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’s
>> what’s causing the transaction to fail.
>
> Alban/Adrian,
>
>> I get the impression that you’re 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=# \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
Looks to me you have a left over unresolved transaction in your psql
session. The easiest solution if that is the case is to exit the session
and start a new session to run the script.
>
> Line 1 is the BEGIN; statement; line 69 is the last row of data to be
> inserted.
>
> Thanks,
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2024-06-19 20:54:35 | Re: Transaction issue |
Previous Message | Rich Shepard | 2024-06-19 20:33:18 | Re: Transaction issue |