Re: Access to old versions of a row - Mailing list pgsql-bugs

From Andres Freund
Subject Re: Access to old versions of a row
Date
Msg-id 20231009235530.jsje2lgvvtbargdx@awork3.anarazel.de
Whole thread Raw
In response to Re: Access to old versions of a row  (Vik Fearing <vik@postgresfriends.org>)
List pgsql-bugs
Hi,

On 2023-10-08 21:35:15 +0200, Vik Fearing wrote:
> On 10/8/23 16:25, Matthias Apitz wrote:
> > 
> > As long as the vacuum is not run, older versions of a given row should
> > be "somewhere". Is there a way to read them?

(auto-)vacuum not having processed a table doesn't guarantee that row versions
have not been removed. Most importantly, on-access pruning can lead to row
versions being removed.  There's also the issue that the toast table could
have been autovacuumed independently from the "main" table.


> No.
> 
> But there is a pg_dirtyread extension that can do it.
> https://github.com/df7cb/pg_dirtyread

Note that there's a lot of potential for bogus data and even crashes when
using something like this. Which is fine when used for data recovery purposes,
but not for many other potential usecases.

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18151: pg_upgradecluster fails when column default refers to column
Next
From: PG Bug reporting form
Date:
Subject: BUG #18152: Join condition is not pushed down to union all subquery