Re: Persist MVCC forever - retain history - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Persist MVCC forever - retain history
Date
Msg-id CAKFQuwZV_rkfPSTOWvq=YYRNi9cXiS7VWR3OeU3H6MCXzLFz5w@mail.gmail.com
Whole thread Raw
In response to Persist MVCC forever - retain history  (Mitar <mmitar@gmail.com>)
Responses Re: Persist MVCC forever - retain history
List pgsql-hackers
On Thursday, July 2, 2020, Mitar <mmitar@gmail.com> wrote:
 
make queries asking for
results at the particular historical version of table state?

Even for a single table how would you go about specifying this in a user-friendly way?  Then consider joins.
 
Is this something I would have to run a custom version of PostgreSQL
or is this possible through an extension of sort?

 If by “this” you mean leveraging MVCC you don’t; it isn’t suitable for persistent temporal data.

The fundamental missing piece is that there is no concept of timestamp in MVCC. Plus, wrap-around and freezing aren’t just nice-to-have features.

David J.

pgsql-hackers by date:

Previous
From: Mitar
Date:
Subject: Persist MVCC forever - retain history
Next
From: Thomas Munro
Date:
Subject: Re: Persist MVCC forever - retain history