Hi VBI, DBLINK was a great idea. I have written the code to do that and it works perfectly. Regards, Atul Goel -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Adrian von Bidder Sent: 16 August 2010 12:27 To: pgsql-general@xxxxxxxxxxxxxx Subject: Re: good exception handling archiecutre Heyho! [[ logging from postgres ]] I think you can use dblink to do this - everything you do via dblink happens in a separate db session and so it shouldn't be affected by what happens in your transaction. Depending on your requirements, system resources may be an issue though (you're opening a full additional db session.) cheers -- vbi -- Although this syntax is required by the SQL standard, it's not clear what the standard expects it to do, except that it's most likely not what we were doing. -- PostgreSQL 8.3 release notes This e-mail is confidential and should not be used by anyone who is not the original intended recipient. Global DataPoint Limited does not accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Global DataPoint Limited. No contracts may be concluded on behalf of Global DataPoint Limited by means of e-mail communication. Global DataPoint Limited Registered in England and Wales with registered number 3739752 Registered Office Middlesex House, 34-42 Cleveland Street, London W1T 4LB -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
