Re: good exception handling archiecutre - Mailing list pgsql-general

From Adrian von Bidder
Subject Re: good exception handling archiecutre
Date
Msg-id 201008161326.58868@fortytwo.ch
Whole thread Raw
In response to Re: good exception handling archiecutre  (<Atul.Goel@globaldatapoint.com>)
Responses Re: good exception handling archiecutre
List pgsql-general
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

Attachment

pgsql-general by date:

Previous
From: Torsten Zühlsdorff
Date:
Subject: Re: InitDB: Bad system call
Next
From: Matthew Wilson
Date:
Subject: How to refer to computed columns from other computed columns?