Re: per-tablespace random_page_cost/seq_page_cost
От | Dimitri Fontaine |
---|---|
Тема | Re: per-tablespace random_page_cost/seq_page_cost |
Дата | |
Msg-id | E1A5F227-1427-4AC5-AC4F-FE3E0E5C0E0C@hi-media.com обсуждение исходный текст |
Ответ на | Re: per-tablespace random_page_cost/seq_page_cost (Greg Stark <gsstark@mit.edu>) |
Ответы |
Re: per-tablespace random_page_cost/seq_page_cost
Re: per-tablespace random_page_cost/seq_page_cost |
Список | pgsql-hackers |
Hi, excuse the quoting style... and the intrepid nature of the following content... -- dim Le 1 nov. 2009 à 13:43, Greg Stark <gsstark@mit.edu> a écrit : > We could have a column for all booleans, a column for all integers, > etc. but that's not really any more normalized than having a single > column for all the types with a rule for how to marshal each value > type. Thé other day, on IRC, someone wanted a dynamic table accepting value in whichever column you name. That would probably mean having a special INSERT INTO which ALTER TABLE ... ADD COLUMN ... for you. Maybe INSERT INTO ... WITH ADD COLUMN OPTION; This sure looks suspicious, but the asking came from another product and it seems that could help here too. Oh and you get text columns I guess, by default...
В списке pgsql-hackers по дате отправления: