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

On Sat, 2008-01-12 at 16:22 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > ... So if we did this via an installable module approach then we
> > would be able to use it much sooner for upgrading to 8.3, rather than
> > waiting for 8.4
>
> I think it borders on ludicrous to imagine making this work with just an
> installable module and no core-code changes. So no, I refuse to spend
> any time helping to design an implementation for 8.3.

Refuse is a strong word, so apologies if I've offended.

I already know how to write it, the main question was how dangerous is
it and I think we answered that. Misuse seems to be the issue you seem
to be worried about. In the wrong hands it could prove to be a Foot Gun
with a larger than normal kill zone.

Dangerous enough that you actively want me to not write it? Or just
saying you're not sure it can be done?

> It'll be a hard enough problem to make this work for 8.4.

Agreed.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Schiltknecht 2008-01-14 09:49:34 Re: Declarative partitioning grammar
Previous Message Simon Riggs 2008-01-14 09:22:01 Re: Postgresql Materialized views