| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | "Li, Yong" <yoli(at)ebay(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Bagga, Rishu" <bagrishu(at)amazon(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Debnath, Shawn" <sdn(at)ebay(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, "Shyrabokau, Anton" <antons(at)ebay(dot)com> |
| Subject: | Re: Proposal to add page headers to SLRU pages |
| Date: | 2024-03-08 21:22:30 |
| Message-ID: | 3ee88744547f6865fe2f48b2b6f058a50796cb91.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2024-03-06 at 12:01 +0000, Li, Yong wrote:
> Rebase the patch against the latest HEAD.
The upgrade logic could use more comments explaining what's going on
and why. As I understand it, it's a one-time conversion that needs to
happen between 16 and 17. Is that right?
Was the way CLOG is upgraded already decided in some earlier
discussion?
Given that the CLOG is append-only and gets truncated occasionally, I
wonder whether we can just have some marker that xids before some
number are the old CLOG, and xids beyond that number are in the new
CLOG. I'm not necessarily suggesting that; just an idea.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2024-03-08 21:56:47 | Re: Streaming read-ready sequential scan code |
| Previous Message | Jeff Davis | 2024-03-08 21:02:53 | Re: Proposal to add page headers to SLRU pages |