| 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: | 1200169510.4266.1378.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-12 20:28:32 | Re: A note about SIGTERM illusion and reality |
| Previous Message | Arunachalam Parthasarathy | 2008-01-12 20:11:04 | getting out boolean value from PQgetValue function |