Re: Transactions, Triggers and Error Messages - Mailing list pgsql-general

From Ledina Hido
Subject Re: Transactions, Triggers and Error Messages
Date
Msg-id 07C2E4F1-FAC8-4FD9-876B-8AC99CE4BC1B@ecs.soton.ac.uk
Whole thread Raw
In response to Re: Transactions, Triggers and Error Messages  (Ledina Hido <lh1101@ecs.soton.ac.uk>)
Responses Re: Transactions, Triggers and Error Messages
List pgsql-general

On Tue, Nov 08, 2005 at 11:03:50PM +0000, Ledina Hido wrote:
> Quoting Tom Lane <tgl@sss.pgh.pa.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  

Yes.

> this error? And if so how can I "catch" the exception. Sorry for my  

http://lnk.nu/postgresql.org/5sl.html


Thinking about it, the EXCEPTION statement would be inside my user-defined function (where I raise the exception in the first place), so I cannot see how that would help. As far as I could understand, I cannot call "ROLLBACK" (which is what I want to do) inside a user defined function. I tried calling it and it was simply ignored. Or am I missing something here?

pgsql-general by date:

Previous
From: Ledina Hido
Date:
Subject: Re: Transactions, Triggers and Error Messages
Next
From: "Keith C. Perry"
Date:
Subject: clustering by partial indexes