Re: Scaling SELECT:s with the number of disks on a stripe

From: Peter Schuller
Subject: Re: Scaling SELECT:s with the number of disks on a stripe
Date: ,
Msg-id: 20070402103443.GA57038@hyperion.scode.org
(view: Whole thread, Raw)
In response to: Re: Scaling SELECT:s with the number of disks on a stripe  ("Marc Mamin")
List: pgsql-performance

Tree view

Scaling SELECT:s with the number of disks on a stripe  (Peter Schuller, )
 Re: Scaling SELECT:s with the number of disks on a stripe  ("Marc Mamin", )
  Re: Scaling SELECT:s with the number of disks on a stripe  (Peter Schuller, )
 Re: Scaling SELECT:s with the number of disks on a stripe  (Andrew - Supernews, )
  Re: Scaling SELECT:s with the number of disks on a stripe  (Peter Schuller, )
 Re: Scaling SELECT:s with the number of disks on a stripe  (Andrew - Supernews, )
  Re: Scaling SELECT:s with the number of disks on a stripe  (Peter Schuller, )
   Re: Scaling SELECT:s with the number of disks on a stripe  (Dave Cramer, )
 Re: Scaling SELECT:s with the number of disks on a stripe  (Andrew - Supernews, )
  Re: Scaling SELECT:s with the number of disks on a stripe  (Peter Schuller, )

Hello,

> If you are dealing with timed data or similar, you may consider to
> partition your table(s).

Unfortunately this is not the case; the insertion is more or less
random (not quite, but for the purpose of this problem it is).

Thanks for the pointers though. That is sure to be useful in some
other context down the road.

--
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <>'
Key retrieval: Send an E-Mail to 
E-Mail:  Web: http://www.scode.org


Attachment

pgsql-performance by date:

From: "Alex Deucher"
Date:
Subject: postgres 7.4 vs. 8.x redux
From: Andrew - Supernews
Date:
Subject: Re: Scaling SELECT:s with the number of disks on a stripe