Re: per-tablespace random_page_cost/seq_page_cost - Mailing list pgsql-hackers

From Robert Haas
Subject Re: per-tablespace random_page_cost/seq_page_cost
Date
Msg-id 603c8f070911021334u44137be8s9bb53d5b7c59f136@mail.gmail.com
Whole thread Raw
In response to Re: per-tablespace random_page_cost/seq_page_cost  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: per-tablespace random_page_cost/seq_page_cost
List pgsql-hackers
On Mon, Nov 2, 2009 at 4:11 PM, Dimitri Fontaine <dfontaine@hi-media.com> wrote:
> 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...

If you want to start a discussion about a topic that is completely
unrelated to this one, then please start a new thread.

...Robert


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Next
From: Robert Haas
Date:
Subject: Re: per-tablespace random_page_cost/seq_page_cost