Nested transaction workaround?

From: "John Sidney-Woollett" <johnsw(at)wardbrook(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Nested transaction workaround?
Date: 2004-01-13 12:47:03
Message-ID: 3609.192.168.0.64.1073998023.squirrel@mercury.wardbrook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Is it possible to use the dblink and dblink_exec features from inside
pl/pgsql functions to mimic the behaviour of nested transactions by
calling another function or executing some SQL via the dblink (into the
same database)?

Does the SQL statement executed within the dblink sit in its own isolated
transaction/session? And would an error thrown in the dblink statement
abort the enclosing session that initiated the call?

What is the overhead/cost in creating the dblink connection?

I'm asking these questions before trying this out, just in case someone
else has already tried, and either failed or succeeded.

John Sidney-Woollett

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2004-01-13 12:56:46 Re: Drawbacks of using BYTEA for PK?
Previous Message Richard Huxton 2004-01-13 12:31:35 Re: Parse error help needed...