From: | "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com> |
---|---|
To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Clarification on a Time travel feature |
Date: | 2007-10-31 11:44:16 |
Message-ID: | 9362e74e0710310444x6b66dedbh2ab08ecc8b618172@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
There is only one condition under which this would be useful.
Current Scenario:
BEGIN
Select x into var from inventory where y=const;
update inventory..
some more DMLs.
some select into var2;
if (condition based on var2)
use the var;
END;
here i have to fire the first select query all the 100% of the time. Say if
i have a feature to time travel within a transaction, i need to fire that
select query on the probability of the condition based on var2 getting true.
After that implementation
BEGIN;
store command id and increment it into cid;
some DMLS
some select into var2
if(condition based on var2)
select into :var as of cid;
I know this is a small use-case. But if you think about it, the
implementation is very easy. It wouldn't take much time to implement it.
Thanks,
Gokul.
On 10/31/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
>
> Gokulakannan Somasundaram wrote:
> > a) Is there a proposal in place for going back in time within a
> transaction?
>
> Within a transaction? No, can't remember one. Doesn't sound very useful.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>
--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Groups.
(www.alliedgroups.com)
From | Date | Subject | |
---|---|---|---|
Next Message | Sheikh Amjad | 2007-10-31 12:21:35 | Postgresql 8.3 beta crash |
Previous Message | Gokulakannan Somasundaram | 2007-10-31 11:38:49 | Re: Clarification on a Time travel feature |