| From: | Andy Fan <zhihuifan1213(at)163(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Deleting older versions in unique indexes to avoid page splits |
| Date: | 2024-11-08 00:38:49 |
| Message-ID: | 87msiawodi.fsf@163.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andy Fan <zhihuifan1213(at)163(dot)com> writes:
> (3). DELETE does generate new index entry, but we might not touch
> the indexes at all during deletes (*except the index we used for index
> scan*).
I still not check the code right now (it may still take times for me
even I understand the overall design). So do we need to mark the
"garbage" hints for DELETE with a index scan? The case in my mind is:
CREATE TABLE t(a INT, B int);
CREATE INDEX t_a_idx on t(a);
CREATE INDEX t_b_idx on t(b);
DELETE FROM t WHERE b = 1;
If the delete goes with Index Scan of t_b_idx, we still have the chances
to mark hints on t_b_idx, so that it can be useful during index split?
--
Best Regards
Andy Fan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-11-08 00:41:10 | Re: Changing the state of data checksums in a running cluster |
| Previous Message | Jacob Champion | 2024-11-08 00:38:45 | Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible |