From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
Cc: | Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Tablespace and cpu costs |
Date: | 2004-08-19 01:40:23 |
Message-ID: | 41240507.5070909@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The first is to add a parameter to CREATE TABLESPACE and ALTER TABLESPACE
> called RANDOMPAGECOST (or something like that) which allows users to set
> the random page cost for a given tablespace. I'm undecided as to whether
> they should be able to set the sequential scan cost. That seems
> reasonable too at first look.
>
> The second option is to have a pg_tablespace.conf file which defines
> tablespace specific settings in some way or another.
>
> Either way, the data will be feed into the planner so that the costing
> routines will be able to use them.
>
> Anyone else got some thoughts on how we could do this in a cleaner manner?
Yes, exactly like we have ALTER USER SET blah=foo; and ALTER DATABASE
SET blah = foo;
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-19 01:42:37 | Re: PGPASSWORD and client tools |
Previous Message | Bruce Momjian | 2004-08-19 01:39:27 | Re: tablespace and sequences? |