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 09:32:26
Message-ID: 1200130346.4266.1263.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2008-01-11 at 19:23 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > For (2) there's a very simple way of transferring the data between
> > sessions:
> > a) we connect on session 1 as a serializable transaction
> > b) we ask session 1 for its snapshot
> > c) we then connect on session 2 as a serializable transaction
> > d) we then execute "select replace_serializable_snapshot(...)"
>
> [ blanches... ] Can you say "security hole"?

Static on the line, sorry.

I'm hearing "useful superuser-only capability". ;-)

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Schiltknecht 2008-01-12 09:46:07 Re: Some ideas about Vacuum
Previous Message Tom Lane 2008-01-12 04:12:14 Re: Psql command-line completion bug