Re: Transactions, Triggers and Error Messages

From: Ledina Hido <lh1101(at)ecs(dot)soton(dot)ac(dot)uk>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Transactions, Triggers and Error Messages
Date: 2005-11-08 23:03:50
Message-ID: 70227D27-C5BB-4691-A153-8B1711634648@ecs.soton.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Quoting Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> What are you running this in? ISTM this is a problem with bad
structure
> of client-side code, not something to be fixed on the server side.
>
> regards, tom lane

I'm using pgAdmin3. Basically when I run the query the first time it
gives the correct error but if I re-run it, then it says "ERROR:
current transaction is aborted, commands ignored until end of
transaction block". Should I be doing something else, ie should I be
explicitly rolling back once the exception is raised so I don't get
this error? And if so how can I "catch" the exception. Sorry for my
ignorance :(

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2005-11-09 00:18:36 Re: Beyond the 1600 columns limit on windows
Previous Message Tom Lane 2005-11-08 22:42:30 Re: Transactions, Triggers and Error Messages