From: | Florian Weimer <fweimer(at)redhat(dot)com> |
---|---|
To: | Stefan Keller <sfkeller(at)gmail(dot)com>, pgsql-general List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres as In-Memory Database? |
Date: | 2014-04-07 06:15:38 |
Message-ID: | 5342428A.6000506@redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/02/2014 12:32 AM, Stefan Keller wrote:
> It also mentions an insert-only technique: "This approach has been
> adopted before in POSTGRES [21] in 1987 and was called "time-travel".
> I would be interested what "time-travel" is and if this is still used by
> Postgres.
Back in the old days, PostgreSQL never deleted any tuples. Rows were
deleted by writing the deletion time into a column. As a result, you
could go back to old data just by telling PostgreSQL to report rows
which where visible at a given time.
Obviously, this approach precluded use of PostgreSQL in many scenarios.
For example, you wouldn't want to use it as your web application
session store.
--
Florian Weimer / Red Hat Product Security Team
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Keller | 2014-04-07 08:29:33 | Re: Postgres as In-Memory Database? |
Previous Message | Francisco Olarte | 2014-04-06 18:31:56 | Re: Any way to insert rows with ID used in another column |