| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Kyotaro HORIGUCHI" <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Lifetime of commit timestamps |
| Date: | 2023-11-17 18:39:14 |
| Message-ID: | c10c558e-c2cc-40f0-b0b8-38d1e806e2f1@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-11-17 18:39:46 | Re: mxid_age() and age(xid) appear undocumented |
| Previous Message | Tom Lane | 2023-11-17 18:18:28 | Re: On non-Windows, hard depend on uselocale(3) |