Re: Persist MVCC forever - retain history

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Mitar <mmitar(at)gmail(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Persist MVCC forever - retain history
Date: 2020-07-02 19:12:50
Message-ID: CAKFQuwZV_rkfPSTOWvq=YYRNi9cXiS7VWR3OeU3H6MCXzLFz5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, July 2, 2020, Mitar <mmitar(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2020-07-02 19:16:21 Re: Persist MVCC forever - retain history
Previous Message Mitar 2020-07-02 18:55:38 Persist MVCC forever - retain history