X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EC94F536AD for ; Tue, 10 May 2005 07:03:36 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12926-01 for ; Tue, 10 May 2005 10:03:28 +0000 (GMT) Received: from mail49.messagelabs.com (mail49.messagelabs.com [193.109.255.19]) by svr1.postgresql.org (Postfix) with SMTP id B87E753892 for ; Tue, 10 May 2005 07:03:25 -0300 (ADT) X-VirusChecked: Checked X-Env-Sender: alexs@advfn.com X-Msg-Ref: server-5.tower-49.messagelabs.com!1115719406!172026!1 X-StarScan-Version: 5.4.11; banners=-,-,- X-Originating-IP: [212.161.99.149] Received: (qmail 8218 invoked from network); 10 May 2005 10:03:26 -0000 Received: from mail.advfn.com (212.161.99.149) by server-5.tower-49.messagelabs.com with SMTP; 10 May 2005 10:03:26 -0000 Received: from [213.86.19.101] (helo=[192.168.0.185]) by mail.advfn.com with esmtp (Exim 4.22) id 1DVRaI-0008GJ-0E for pgsql-performance@postgresql.org; Tue, 10 May 2005 11:03:26 +0100 Mime-Version: 1.0 (Apple Message framework v728) Content-Transfer-Encoding: 7bit Message-Id: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: pgsql-performance@postgresql.org From: Alex Stapleton Subject: Partitioning / Clustering Date: Tue, 10 May 2005 11:03:26 +0100 X-Mailer: Apple Mail (2.728) X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200505/135 X-Sequence-Number: 12299 What is the status of Postgres support for any sort of multi-machine scaling support? What are you meant to do once you've upgraded your box and tuned the conf files as much as you can? But your query load is just too high for a single machine? Upgrading stock Dell boxes (I know we could be using better machines, but I am trying to tackle the real issue) is not a hugely price efficient way of getting extra performance, nor particularly scalable in the long term. So, when/is PG meant to be getting a decent partitioning system? MySQL is getting one (eventually) which is apparently meant to be similiar to Oracle's according to the docs. Clusgres does not appear to be widely/or at all used, and info on it seems pretty thin on the ground, so I am not too keen on going with that. Is the real solution to multi- machine partitioning (as in, not like MySQLs MERGE tables) on PostgreSQL actually doing it in our application API? This seems like a less than perfect solution once we want to add redundancy and things into the mix.