Re: column ordering, was Re: [PATCHES] Enums patch v2

Поиск
Список
Период
Сортировка
От Martijn van Oosterhout
Тема Re: column ordering, was Re: [PATCHES] Enums patch v2
Дата
Msg-id 20061219162504.GC21385@svana.org
обсуждение исходный текст
Ответ на column ordering, was Re: [PATCHES] Enums patch v2  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: column ordering, was Re: [PATCHES] Enums patch v2  (Robert Treat <xzilla@users.sourceforge.net>)
Список pgsql-hackers
On Tue, Dec 19, 2006 at 10:48:41AM -0500, Andrew Dunstan wrote:
> Sure, but the only sane way I can think of to do that would be have
> separate logical and physical orderings, with a map between the two. I
> guess we'd need to see what the potential space savings would be and
> establish what the processing overhead would be, before considering it.
> One side advantage would be that it would allow us to do the often
> requested "add column at position x".

A patch to allow seperate physical and logical orderings was submitted
and rejected. Unless something has changed on that front, any
discussion in this direction isn't really useful.

Once this is possible it would allow a lot of simple savings. For
example, shifting all fixed width fields to the front means they can
all be accessed without looping through the previous columns, for
example.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

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

Предыдущее
От: "Zeugswetter Andreas ADI SD"
Дата:
Сообщение: Re: pg_restore fails with a custom backup file
Следующее
От: Stephen Frost
Дата:
Сообщение: ERROR: tuple concurrently updated