| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Greg Burd <greg(at)burd(dot)me>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support for 8-byte TOAST values, round two |
| Date: | 2026-09-14 05:12:18 |
| Message-ID: | aqeCMqmIqDJV42D5@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 11, 2026 at 01:03:27PM -0300, Marcos Pegoraro wrote:
> Did you forget to mention the new REPACK command on create_table.SGML file ?
Yep, the statement is equally true with REPACK ("such as" means "like"
to me, meaning that the list could remain rather loose of details, but
I don't mind the addition).
I have amended the documentation. More importantly, I have also added
some tests in the v18 sent upthread, checking that the TOAST table
definition does not change across repack queries even after an ALTER
TABLE has the idea to change toast_value_type if a TOAST table already
exists.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2026-09-14 05:34:25 | RE: Review items for EXCEPT TABLE publication |
| Previous Message | Richard Guo | 2026-09-14 05:10:21 | Re: remove_useless_joins vs. bug #19560 |