| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID |
| Date: | 2025-11-19 04:36:19 |
| Message-ID: | A7F5E502-4ED7-44E4-95C6-32D99336F49C@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 18 Nov 2025, at 23:54, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> Are you arguing that the xl_btree_split record should include the cycleid?
Yes.
> I see that systems that are built on this architecture do something
> along these lines:
> https://github.com/neondatabase/postgres/commit/a9b92820c5d14dbff8f59ab65ffdaae92ab9c3c8
Thanks for the link. This solution seems surprisingly complicated.
> However, that seems well out of scope for core Postgres. At least for
> the foreseeable future.
Yes, I agree. It's just a case when redo routines do not match original execution, and it seemed interesting to me. I understand that for core Postgres it's extra overhead in WAL record only for a beautification.
Thanks!
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shinya Kato | 2025-11-19 05:10:04 | Re: Add mode column to pg_stat_progress_vacuum |
| Previous Message | Chao Li | 2025-11-19 04:14:03 | Re: Row pattern recognition |