On Fri, 2005-06-03 at 18:04, Matt Miller wrote:
> > > a way to enable a function to commit a unit of work that
> > > does not affect the caller's transaction.
>
> > accomplish autonomous transactions in PL/pgSQL
> > by just using dblink_connect, dblink_open, dblink_exec,
> > and dblink_close?
>
>
> > a way to enable a function to commit a unit of work that
> > does not affect the caller's transaction.
> accomplish autonomous transactions in PL/pgSQL
> by just using dblink_connect, dblink_open, dblink_exec,
> and dblink_close?
My initial tests lead me to believe that dblink is a simple and
> > a way to enable a function to commit a unit of work that
> > does not affect the caller's transaction.
> Is dblink a possible answer? (it's a contrib package.)
Very interesting. When you earlier mentioned dblink I found only
DBLink-TDS on pgFoundry, and I dismissed it since I'm not accessin
On Fri, 2005-06-03 at 15:10, Matt Miller wrote:
> > > a way to enable a function to commit a unit of work that
> > > does not affect the caller's transaction.
>
> > you can establish an independent connection within a function in, say,
> > PL/Perl or PL/Python.
>
> Okay, multiple connections seem
> > a way to enable a function to commit a unit of work that
> > does not affect the caller's transaction.
> you can establish an independent connection within a function in, say,
> PL/Perl or PL/Python.
Okay, multiple connections seems to be my best shot. However, I would
like standard develope
On Wed, 2005-06-01 at 10:52, Alvaro Herrera wrote:
> On Wed, Jun 01, 2005 at 03:38:01PM +, Matt Miller wrote:
> > I'm willing to use a different language, or even the libpq API if
> > necessary.
>
> If you really need autonomous transactions, you can establish an
> independent connection with
On Wed, Jun 01, 2005 at 03:38:01PM +, Matt Miller wrote:
> I'm looking for a way to enable a function to commit a unit of work that
> does not affect the caller's transaction. I'm coming from the Oracle
> world where I've used the "autonomous_transaction" pragma of PL/SQL to
> do this. I'm ne
I'm looking for a way to enable a function to commit a unit of work that
does not affect the caller's transaction. I'm coming from the Oracle
world where I've used the "autonomous_transaction" pragma of PL/SQL to
do this. I'm new to Postgres, but I'm hopeful that I can move our
systems from Oracl
