X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id B7B10D1C510 for ; Thu, 14 Aug 2003 21:48:08 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 01591-01 for ; Thu, 14 Aug 2003 18:48:00 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id BD864D1F443 for ; Thu, 14 Aug 2003 18:47:42 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h7ELl1Q11939; Thu, 14 Aug 2003 17:47:01 -0400 (EDT) From: Bruce Momjian Message-Id: <200308142147.h7ELl1Q11939@candle.pha.pa.us> Subject: Re: Perfomance Tuning In-Reply-To: To: Jeff Date: Thu, 14 Aug 2003 17:47:01 -0400 (EDT) Cc: Christopher Browne , "pgsql-performance@postgresql.org" X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/270 X-Sequence-Number: 3086 Jeff wrote: > > You raise a good point vis-a-vis the thought of spawning multiple > > readers; that could conceivably be a useful approach to improve > > performance for very large queries. If you could "stripe" the tables > > in some manner so they could be doled out to multiple worker > > processes, that could indeed provide some benefits. If there are > > three workers, they might round-robin to grab successive pages from > > the table to do their work, and then end with a merge step. > > The way informix does this is two fold: > 1. it handles the raw disks, it knows where table data is > 2. it can "partition" tables in a number of ways: round robin, > concatination or expression (Expression is nifty, allows you to use a > basic "where" clause to decide where to put data. ie > create table foo ( > a int, > b int, > c int ) fragment on c > 0 and c < 100 in dbspace1, c > 100 c < 200 in > dbspace 2; > > that kind of thing. > and yeah, I would not expect to see it for a long time.. Without threading > it would be rather difficult to implement.. but who knows what the future > will bring us. The big question is whether the added complexity is worth it. I know Informix 5 was faster than Informix 7 on single CPU machines for quite a while. It might still be true. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073