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

From David Fetter
Subject Re: per-tablespace random_page_cost/seq_page_cost
Date
Msg-id 20091028012054.GA3860@fetter.org
Whole thread Raw
In response to Re: per-tablespace random_page_cost/seq_page_cost  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: per-tablespace random_page_cost/seq_page_cost
Re: per-tablespace random_page_cost/seq_page_cost
List pgsql-hackers
On Tue, Oct 27, 2009 at 09:13:29PM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.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.

Cheers
David.
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Next
From: Fujii Masao
Date:
Subject: Re: [ADMIN] pg_standby doesnt't work