Skip site navigation (1) Skip section navigation (2)

Re: per-tablespace random_page_cost/seq_page_cost

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Date: 2009-11-01 15:02:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Nov 1, 2009, at 7:43 AM, Greg Stark <gsstark(at)mit(dot)edu> wrote:

> On Sat, Oct 31, 2009 at 6:04 PM, Robert Haas <robertmhaas(at)gmail(dot)com>  
> wrote:
>> Looking at this a little more, it seems that part of the motivation
>> for the existing design is that user-created AMs might require
>> arbitrary options, which therefore can't be wired into the system
>> catalogs.  There's no equivalent for tablespaces (we could add one
>> some day, I suppose), so there's less intrinsic reason to think we
>> have to do it that way.
> Can't custom modules define arbitrary options which they declare can
> be defined per tablespace?

Yeah, probably we can support that for free, although I'm not sure  
there is much demand for it.

> 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
> - how to marshal each value
> type.

That has no advantages and several disadvantages AFAICS.

I don't want to get sidetracked here. The real issue is the one I  
discussed in the portion of the email you didn't quote...


In response to

pgsql-hackers by date

Next:From: Marko TiikkajaDate: 2009-11-01 15:12:36
Subject: Re: WIP: push AFTER-trigger execution into ModifyTable node
Previous:From: Greg StarkDate: 2009-11-01 12:43:57
Subject: Re: per-tablespace random_page_cost/seq_page_cost

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group