Re: Transaction Snapshot Cloning - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Transaction Snapshot Cloning
Date
Msg-id 1200169510.4266.1378.camel@ebony.site
Whole thread Raw
In response to Re: Transaction Snapshot Cloning  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Transaction Snapshot Cloning  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 2008-01-12 at 11:57 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > On Fri, 2008-01-11 at 19:23 -0500, Tom Lane wrote:
> >> [ blanches... ]  Can you say "security hole"?
> 
> > Static on the line, sorry. 
> > I'm hearing "useful superuser-only capability". ;-)
> 
> It would be far *more* useful if it didn't have to be superuser-only.
> And since the actual details of the snapshot content are really of
> zero interest to the user, I think making it pass through his hands
> is simply misdesign.

No, its deliberate, because I want this to work on prior releases. I
didn't clearly explain that, sorry.

For 8.4+ I will design the internal route for this feature.

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: "Arunachalam Parthasarathy"
Date:
Subject: getting out boolean value from PQgetValue function
Next
From: Tom Lane
Date:
Subject: Re: A note about SIGTERM illusion and reality