| From: | Alex Friedman <alexf01(at)gmail(dot)com> |
|---|---|
| To: | John Naylor <johncnaylorls(at)gmail(dot)com> |
| Cc: | Sami Imseih <samimseih(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Doc fix of aggressive vacuum threshold for multixact members storage |
| Date: | 2025-03-04 14:22:45 |
| Message-ID: | CACbFw62-WR9sgwXv8nQ7Co0szBOrkqmcHhRP7T+s0b9VuVmuUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>I decided to leave this out, since I just remembered that the most
> likely change is actually to move to 64-bit offsets, as was proposed
> here and has some enthusiastic support:
>
> https://www.postgresql.org/message-id/CACG=ezaWg7_nt-8ey4aKv2w9LcuLthHknwCawmBgEeTnJrJTcw@mail.gmail.com
Thanks for the review and the draft, looks good to me, and I'm okay
with doing this without the code comments. However, it seems like that
thread is just the beginning of wider changes (if they indeed happen),
which may impact these calculations as well, and then maybe a doc
update reminder may come in useful?
Best regards,
Alex Friedman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-03-04 14:23:55 | Re: making EXPLAIN extensible |
| Previous Message | Andrew Dunstan | 2025-03-04 14:19:35 | Re: what's going on with lapwing? |