Re: Lazy Snapshots

Поиск
Список
Период
Сортировка
Искать
От
Gokulakannan Somasundaram
Тема
Re: Lazy Snapshots
Дата
Msg-id
9362e74e0908212118v669d67c3l12fa1c9840562276@mail.gmail.com
Ответ на
Re: Lazy Snapshots (simon@2ndquadrant.com)
Список
Дерево обсуждения
Lazy Snapshots "simon@2ndquadrant.com" <simon@2ndquadrant.com>
Re: Lazy Snapshots Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Lazy Snapshots Josh Berkus <josh@agliodbs.com>
Re: Lazy Snapshots "simon@2ndquadrant.com" <simon@2ndquadrant.com>
Re: Lazy Snapshots Tom Lane <tgl@sss.pgh.pa.us>
Re: Lazy Snapshots "simon@2ndquadrant.com" <simon@2ndquadrant.com>
Re: Lazy Snapshots Gokulakannan Somasundaram <gokul007@gmail.com>
Re: Lazy Snapshots Tom Lane <tgl@sss.pgh.pa.us>
Re: Lazy Snapshots Gokulakannan Somasundaram <gokul007@gmail.com>
Hi,
   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
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.

Thanks,
Gokul.
В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Jean-Michel Pouré
Дата:
Сообщение: DELETE syntax on JOINS
FAQ