On Thu, 1 Jul 2004 22:55:56 -0400, Mike Rylander <[EMAIL PROTECTED]>
wrote:
>I was thinking of purely tablespace-based random_page_cost, as that variable
>is tied to the access time of a particular filesystem.
Strictly speaking we'd also need tablespace-based sequential_page_cost.
Servus
Manfre
On Thursday 01 July 2004 08:54 pm, Gavin Sherry wrote:
> On Thu, 1 Jul 2004, Mike Rylander wrote:
> > 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 som
On Thursday 01 July 2004 09:26 pm, Scott Marlowe wrote:
> On Thu, 2004-07-01 at 18:54, Gavin Sherry wrote:
> > On Thu, 1 Jul 2004, Mike Rylander wrote:
> > > On Thursday 01 July 2004 06:43 pm, Gavin Sherry wrote:
> > > > Hi Mike,
> > > >
> > > > In this release, unfortunately not.
> > >
> > > That'
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 ac
I would like to see some tool that reported an semi-accurate value for
random page cost before adding the value per tablespace.
---
Scott Marlowe wrote:
> On Thu, 2004-07-01 at 18:54, Gavin Sherry wrote:
> > On Thu, 1 Jul 20
On Thu, 2004-07-01 at 18:54, Gavin Sherry wrote:
> On Thu, 1 Jul 2004, Mike Rylander wrote:
>
> > 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
On Thu, 1 Jul 2004, Mike Rylander wrote:
> 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
> > h
Hi Mike,
In this release, unfortunately not.
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. :-(
Gavin
On Mon, 28 Jun 2004, Mike Rylander wrote:
> Now that PG will have tablespaces
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
