Re: Lazy Snapshots

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gokulakannan Somasundaram <gokul007(at)gmail(dot)com>
Cc: "simon(at)2ndquadrant(dot)com" <simon(at)2ndquadrant(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lazy Snapshots
Date: 2009-08-22 13:43:31
Message-ID: 8308.1250948611@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> writes:
> I have given some thought in this direction. I am just providing my idea.

> a) Have a structure similar to commit log, which should also store,
> transaction id at which the transaction got committed. Every transaction,
> after committing should update the transaction id at which the commit has
> happened

The maintenance costs and update contention for such a datastructure
would render this completely impractical, even if consulting it were
free.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-22 13:56:22 Re: SIGUSR1 pingpong between master na autovacum launcher causes crash
Previous Message Greg Stark 2009-08-22 11:35:48 Re: [PATCH] plpythonu datatype conversion improvements