| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: REPACK and naming |
| Date: | 2025-09-17 13:36:34 |
| Message-ID: | CAB-JLwZEP7pVWtEjr21hyOrbWcywwSXYbW3xtPGwk_Rrqa0nUg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em qua., 17 de set. de 2025 às 10:17, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:
> That changes logical aspects of a table and so would be done as part of
> alter table, IMO. “AT tbl Rearrange columns (names list) “
>
If this command recreates entirely that table, it is not only a logical
aspect of that table.
REPACK/RETABLE recreates that table as a replacement for VACUUM FULL/CLUSTER
and ALTER TABLE REARRANGE COLUMNS would recreate that table too ?
and both would have USING INDEX to do what CLUSTER does today ? both would
have CONCURRENTLY ?
Being named REPACK or RETABLE or RECREATE TABLE or COMPACT or anything else
could do it all.
regards
Marcos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-09-17 13:37:45 | Re: REPACK and naming |
| Previous Message | Mircea Cadariu | 2025-09-17 13:35:53 | Re: [BUG] temporary file usage report with extended protocol and unnamed portals |