| From: | solai v <solai(dot)cdac(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Nikita Malakhov <hukutoc(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: problems with toast.* reloptions |
| Date: | 2026-06-10 11:41:36 |
| Message-ID: | CAF0whuf=D3AncYxfuwK05_TFY+4nK8-teTYtoiu7Zp-pzVAPDQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I tested the v5 patch series on the current HEAD.
The patches applied and built successfully. I verified that TOAST
reloptions are still accepted and stored correctly. I also tested
parent and TOAST reloption combinations, RESET behavior, and VACUUM
processing.
For example, with:
ALTER TABLE toast_test2 SET (vacuum_truncate = false);
ALTER TABLE toast_test2 SET (toast.vacuum_truncate = true);
resetting the parent reloption preserved the explicit TOAST reloption
as expected.
I also verified that VACUUM (PROCESS_MAIN false) correctly processes
only the associated TOAST table.
I did not observe any issues during testing.
Regards,
solai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2026-06-10 11:54:06 | Re: [PATCH v1] [BUG #19516] Skip whole-row projection shortcut for OLD/NEW returning type |
| Previous Message | Chao Li | 2026-06-10 11:38:23 | Re: Fix md5_password_warnings for role/database settings |