| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Euler Taveira <euler(at)eulerto(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Lifetime of commit timestamps |
| Date: | 2023-11-24 22:56:48 |
| Message-ID: | ZWEqMGpdO93gyZ1-@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 17, 2023 at 04:36:44PM -0500, Bruce Momjian wrote:
> On Fri, Nov 17, 2023 at 01:20:46PM -0800, Andres Freund wrote:
> > On 2023-11-17 15:39:14 -0300, Euler Taveira wrote:
> >
> > I think the connection between freezing and removal of commit timestamps is a
> > lot less direct that your suggested docs suggest. There can be no freezing and
> > we'll still remove timestamps (if tuples were deleted/updated). And tuples can
> > be frozen without the committs being truncated (if other tables have an older
> > relfrozenxid).
> >
> > The relevant limiting factor is minimum of all databases datfrozenxid. Which
> > in turn is limited by relfrozenxid of each table in said database. And
> > relfrozenxid is limited by snapshots (and prepared transactions, replication
> > slots, etc).
>
> Okay, I went with more weasel-wording in the attached patch.
Patch applied back to PG 16.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-11-24 23:02:12 | Re: remove deprecated @@@ operator ? |
| Previous Message | Thomas Munro | 2023-11-24 21:11:54 | Re: Improving the comments in pqsignal() |