Re: autonomous transactions - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: autonomous transactions
Date
Msg-id 200801291612.m0TGCP829274@momjian.us
Whole thread Raw
In response to Re: autonomous transactions  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: autonomous transactions  (Bruce Momjian <bruce@momjian.us>)
Re: autonomous transactions  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Simon Riggs wrote:
> On Tue, 2008-01-22 at 20:53 +0100, Pavel Stehule wrote:
> > >
> > > Agreed.  I think Pavel Stehule was doing some experiments with them, I
> > > don't know if he got anywhere.
> > >
> > 
> > I did only first research. Any hack is possible - you can stack
> > current transaction, but real implementation needs similar work like
> > nested transaction :( and it is too low level for me. And some code
> > cleaning is necessary. There are global variables.
> > 
> > And there is most important question about data visibility - is
> > autonomous transaction independent on main transaction (isolation)?
> > You have to thing about deadlock, about reference integrity, etc. This
> > task isn't simple.
> 
> Yes, I think autonomous transactions should be on the TODO. They're
> useful for
> - error logging
> - auditing
> - creating new partitions automatically
> 
> Plus I think we'd be able to improve the code for CREATE INDEX under
> HOT, and probably a few other wrinkly bits of code.

Added to TODO:

* Add anonymous transactions
 http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php


--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable
Next
From: Bruce Momjian
Date:
Subject: Re: autonomous transactions