Re: [PATCHES] Enums patch v2

Поиск
Список
Период
Сортировка
Искать
От
Tom Dunstan
Тема
Re: [PATCHES] Enums patch v2
Дата
Msg-id
4588946E.90505@tomd.cc
Ответ на
Список
Дерево обсуждения
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Stephen Frost <sfrost@snowman.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Martijn van Oosterhout <kleptog@svana.org>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Stephen Frost <sfrost@snowman.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Martijn van Oosterhout <kleptog@svana.org>
Re: column ordering, was Re: [PATCHES] Enums patch v2 "Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Andrew Dunstan <andrew@dunslane.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Martijn van Oosterhout <kleptog@svana.org>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Martijn van Oosterhout <kleptog@svana.org>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Martijn van Oosterhout <kleptog@svana.org>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Andrew Dunstan <andrew@dunslane.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 "Jim C. Nasby" <jim@nasby.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Bruce Momjian <bruce@momjian.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Andrew Dunstan <andrew@dunslane.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Gregory Stark <gsstark@mit.edu>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 "Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>
Re: column ordering, was Re: [PATCHES] Enums patch v2 "Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Martijn van Oosterhout <kleptog@svana.org>
Re: column ordering, was Re: [PATCHES] Enums patch v2 "Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Russell Smith <mr-russ@pws.com.au>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Andrew Dunstan <andrew@dunslane.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Stephen Frost <sfrost@snowman.net>
Re: column ordering, was Re: [PATCHES] Enums patch Bruce Momjian <bruce@momjian.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Tom Lane <tgl@sss.pgh.pa.us>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Russell Smith <mr-russ@pws.com.au>
Re: column ordering, was Re: [PATCHES] Enums patch "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Peter Eisentraut <peter_e@gmx.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Kenneth Marshall <ktm@it.is.rice.edu>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Martijn van Oosterhout <kleptog@svana.org>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Andrew Dunstan <andrew@dunslane.net>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Richard Huxton <dev@archonet.com>
Re: column ordering, was Re: [PATCHES] Enums patch v2 Peter Eisentraut <peter_e@gmx.net>
Alvaro Herrera wrote:
> I don't, because there are always those that are knowledgeable enough to
> know how to reduce space lost to padding.  So it would be nice to have
> 2-byte enums on-disk, and resolve them based on the column's typid.  But
> then, I'm not familiar with the patch at all so I'm not sure if it's
> possible.

Not with this patch, and AFAIK not possible generally, without writing 
separate I/O functions for each type. I'd love to be able to do that, 
but I don't think it's possible currently. The main stumbling block is 
the output function (and cast-to-text function), because output 
functions do not get provided the oid of the type that they're dealing 
with, for security reasons IIRC. It was never clear to me why I/O 
functions should ever be directly callable by a user (and hence open to 
security issues), but apparently it was enough to purge any that were 
designed like that from the system, so I wasn't going to go down that 
road with the patch.

Cheers

Tom


В списке pgsql-hackers по дате отправления
От: Peter Eisentraut
Дата:
От: Joshua D. Drake
Дата:
FAQ