Re: Lifetime of commit timestamps - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Lifetime of commit timestamps
Date
Msg-id ZVfUp4nLj7RnqErM@momjian.us
Whole thread Raw
In response to Re: Lifetime of commit timestamps  ("Euler Taveira" <euler@eulerto.com>)
List pgsql-hackers
On Fri, Nov 17, 2023 at 03:39:14PM -0300, Euler Taveira wrote:
> On Mon, Nov 13, 2023, at 9:47 PM, Bruce Momjian wrote:
> 
>     Is this documentation change still relevant?
> 
> 
> I think so. AFAICS nothing changed. Unless you read the source code, it is not
> clear that VACUUM removes the information for frozen tuples. They are decoupled
> (but executed in the same routine for convenience), hence, someone can ask why
> the pg_xact_commit_timestamp() returns NULL for a transaction that was executed
> *after* you enable track_commit_timestamp. The answer is the design used a
> existing mechanism to clean up data in order to avoid creating a new one.

Okay, I have developed the attached patch based on Horiguchi-san's
version.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.

Attachment

pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Re: simplehash: preserve consistency in case of OOM
Next
From: Andres Freund
Date:
Subject: Re: lazy_scan_heap() should release lock on buffer before vacuuming FSM