From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Greg Stark <gsstark(at)mit(dot)edu>, Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: per-tablespace random_page_cost/seq_page_cost |
Date: | 2009-10-28 02:01:54 |
Message-ID: | 20091028020153.GP4876@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter escribió:
> On Tue, Oct 27, 2009 at 09:13:29PM -0400, Tom Lane wrote:
> > Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > > I confess that I'm a bit mystified about the design of the
> > > reloptions stuff. It seems kind of odd to store structured data as
> > > text[]; it's kind of the opposite of what I would normally
> > > recommend as good database design.
> >
> > It's definitely a bit EAV-ish :-(. But I don't see any particularly
> > easy way to modify it to store bool/int/float parameters in their
> > native types; do you?
>
> More columns, each of the correct type, with the table constraint that
> at most one may be populated is how I handle stuff like that.
So we would have "spcintoptions", "spcfloatoptions", and so on? (I
don't see the need for the table constraint in this case.)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-10-28 02:10:46 | Re: per-tablespace random_page_cost/seq_page_cost |
Previous Message | Fujii Masao | 2009-10-28 01:37:03 | Re: [HACKERS] pg_standby doesnt't work |