From: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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:37:45 |
Message-ID: | 202509171332.lic5kjycuo7a@alvherre.pgsql |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-Sep-17, David G. Johnston wrote:
> That changes logical aspects of a table and so would be done as part of
> alter table, IMO. “AT tbl Rearrange columns (names list) “
Yes.
> Concretely, maybe we should remove vacuum full from the vacuum command
> page, and just call it out as compatibility spelling of repack on its
> page. Maybe do the same for cluster (I haven’t dived into the new feature
> enough to confidently describe all this yet though).
I think we should list VACUUM FULL as deprecated, document that feature
in the REPACK documentation page, and leave VACUUM FULL in working state
so as not to break existing scripts. Same for CLUSTER.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Those who use electric razors are infidels destined to burn in hell while
we drink from rivers of beer, download free vids and mingle with naked
well shaved babes." (http://slashdot.org/comments.pl?sid=44793&cid=4647152)
From | Date | Subject | |
---|---|---|---|
Next Message | Shlok Kyal | 2025-09-17 13:38:30 | Re: Logical Replication of sequences |
Previous Message | Marcos Pegoraro | 2025-09-17 13:36:34 | Re: REPACK and naming |