Re: Separate the attribute physical order from logical order

Поиск
Список
Период
Сортировка
От Isaac Morland
Тема Re: Separate the attribute physical order from logical order
Дата
Msg-id CAMsGm5cOf=71GiELtDAaX4Qd6WQcyzUzTapsDuHzR1prmLdSdg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Separate the attribute physical order from logical order  (Julien Rouhaud <rjuju123@gmail.com>)
Ответы Re: Separate the attribute physical order from logical order  (Julien Rouhaud <rjuju123@gmail.com>)
Список pgsql-hackers
Дерево обсуждения
On Tue, 28 Jun 2022 at 05:32, Julien Rouhaud <rjuju123@gmail.com> wrote:
I think that supporting at least a way to specify the logical order during the
table creation should be easy to implement (there shouldn't be any
question on whether it needs to invalidate any cache or what lock level to
use), and could also be added in the initial submission without much extra
efforts, which could help with the testing.

I think the meaning of “logical order” (well, the meaning it has for me, at least) implies that the logical order of a table after CREATE TABLE is the order in which the columns were given in the table creation statement.

If there needs to be a way of specifying the physical order separately, that is a different matter.

ALTER TABLE ADD … is another matter. Syntax there to be able to say BEFORE or AFTER an existing column would be nice to have. Presumably it would physically add the column at the end but set the logical position as specified.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Aleksander Alekseev
Дата:
Сообщение: Re: [PATCH] Compression dictionaries for JSONB
Следующее
От: Isaac Morland
Дата:
Сообщение: Re: Making the subquery alias optional in the FROM clause