On Thursday 01 July 2004 06:43 pm, Gavin Sherry wrote:
> Hi Mike,
>
> In this release, unfortunately not.
That't too bad, but it's not that urgent I suppose.
>
> I had some idea early on of putting rand_page_cost in pg_tablespace and
> having the planner have access to it for costing. I didn't actually get
> around to it but. :-(
Well, I haven't looked at the PG source before, but if you have some specific
design ideas I would be glad to help out. I'm just not sure where (or when,
with the official release coming (sort of) soon) to start, but with some
pointers I'll do what I can!
-miker
>
> Gavin
>
> On Mon, 28 Jun 2004, Mike Rylander wrote:
> > Now that PG will have tablespaces I can stick my really high I/O data on
> > a fiberchannel array, and save some money by putting the rest of it (also
> > the majority of it) on less expensive SCSI RAID sets. Will I also be
> > able to tune individual tablespaces with the likes of random_page_cost?
> > Sorry if I missed this somewhere...
> >
> > TIA
> >
> > --miker
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> >
> >
> > !DSPAM:40e47cf853041767292179!
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
