Skip site navigation (1) Skip section navigation (2)

Re: Transaction Snapshot Cloning

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction Snapshot Cloning
Date: 2008-01-12 20:25:10
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
On Sat, 2008-01-12 at 11:57 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2008-01-12 20:28:32
Subject: Re: A note about SIGTERM illusion and reality
Previous:From: Arunachalam ParthasarathyDate: 2008-01-12 20:11:04
Subject: getting out boolean value from PQgetValue function

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group