On Thu, Sep 08, 2005 at 02:53:47PM +0200, Michael Fuhr wrote:
> One way would be to use contrib/dblink to open another connection
> to the database so the status messages could be inserted in a
> separate transaction.
This could do the trick for logging, even writting of a package that would
do all the stuff should not be hard. But what if you want to flush
something processed to db. Consider you are doing massive updates/deletes.
Again in logical blocks. You as a programmer may decide: "ok so far I am
done and even if I crash I want to preserve these changes." It happened
me, that db aborted processing such huge updates with out of memory
message. Would calling stored procedure from stored procedure solved
this? Or if parent procedure is not commited then even called procedure
will not commit?