| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Shiju Sivadazz <shijusivadazz86(at)gmail(dot)com> |
| Subject: | Re: Question about heap_inplace_update and VACUUM behavior |
| Date: | 2026-03-11 12:21:27 |
| Message-ID: | CAJ7c6TP4cfo45FdRwtfVCHXM1+jxOaBOQn7vsfj6Q2fMa1Kr-Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Shiju,
Thanks to your interest in DBMS development and Postgres in particular.
> I would greatly appreciate any clarification or references to relevant documentation or design discussions.
If you go to the systable_inplace_update_begin() definition you will
find that its use cases are very well documented. I recommend using a
modern text editor with goto definition / goto symbol functionality
e.g. VS Code or Zed. This will simplify the exploration of the code a
lot.
Also I believe you are on the REL_17_STABLE branch. I would recommend
choosing `master` which will become REL_19 quite soon.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2026-03-11 12:47:58 | Re: Change initdb default to the builtin collation provider |
| Previous Message | KAZAR Ayoub | 2026-03-11 12:19:18 | Re: Speed up COPY FROM text/CSV parsing using SIMD |