Re: REPACK and naming
От | Robert Haas |
---|---|
Тема | Re: REPACK and naming |
Дата | |
Msg-id | CA+Tgmoaq5zPALxkDXoGaWQpuxbosE0CHAUVg9NkBssjtDjSsfQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: REPACK and naming (Marcos Pegoraro <marcos@f10.com.br>) |
Ответы |
Re: REPACK and naming
|
Список | pgsql-hackers |
On Wed, Sep 17, 2025 at 8:04 AM Marcos Pegoraro <marcos@f10.com.br> wrote: > Em ter., 16 de set. de 2025 às 23:01, Robert Haas <robertmhaas@gmail.com> escreveu: >> I think RETABLE is not a proposal to be taken seriously. That's >> extremely confusing. > > This feature could be used in a future version to rearrange fields in a table, for better padding. > I don't think we have another one available for this purpose. > > CREATE TABLE T(A text, B integer, C bigint, D integer); > > We could have something like > RETABLE T USING(B, D, C, A) > > So REPACK isn't the best for this, if this feature would exist some day. RETABLE just isn't a word. The code sometimes calls this a REWRITE of a table, which would be reasonable. I suspect, though, that changing the column order would end up being a form of ALTER TABLE. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: