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
b) All the transactions- when it starts should have two figures - xmin and
also a transaction id after which nothing has got committed
c) So whenever it sees the records, which are not inside the window, it can
make decision by itself.
i) The ones below xmin and committed are visible
ii) the ones after xmax and committed are not visible
iii) When its something in between, then check the time at which the
commit happened in the structure and make the decision.
Ideally, it would be better to change the structure of commit log itself.
But maintaining an another structure also would help.
In response to
pgsql-hackers by date
|Next:||From: Jean-Michel Pouré||Date: 2009-08-22 07:40:55|
|Subject: DELETE syntax on JOINS|
|Previous:||From: Tom Lane||Date: 2009-08-22 01:55:07|
|Subject: Re: Feedback about Drupal SQL debugging |