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 F41255650D for ; Wed, 23 Feb 2005 21:02:00 +0000 (GMT) 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 36105-06 for ; Wed, 23 Feb 2005 21:01:57 +0000 (GMT) Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by svr1.postgresql.org (Postfix) with ESMTP id 6957656509 for ; Wed, 23 Feb 2005 21:01:56 +0000 (GMT) Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.13.2/8.12.9) with ESMTP id j1NL1wKj005548; (envelope-from ) Wed, 23 Feb 2005 15:01:58 -0600 (CST) Received: from [192.168.1.174] (67-41-93-122.cdrr.qwest.net [67.41.93.122]) (authenticated user=jfmeinel) by server11.icaen.uiowa.edu (8.13.2/smtp-serv-1.7) with ESMTP id j1NL1unk011035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256); (envelope-from ) Wed, 23 Feb 2005 15:01:57 -0600 (CST) Message-ID: <421CEF43.6030207@arbash-meinel.com> Date: Wed, 23 Feb 2005 15:01:55 -0600 From: John Arbash Meinel User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Allgood Cc: pgsql-performance@postgresql.org Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout References: <421cca80.3da18bb5.6940.3b12@smtp.gmail.com> <21021.1109183848@sss.pgh.pa.us> <421CD668.7010503@turbocorp.com> <421CDD83.3070609@arbash-meinel.com> <421CE1FD.80003@turbocorp.com> <421CE699.1060300@arbash-meinel.com> <421CEA85.50506@turbocorp.com> In-Reply-To: <421CEA85.50506@turbocorp.com> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8765F6D17C216B1B0F2EE386" X-Virus-Scanned: ClamAV 0.80/682/Mon Jan 24 12:53:43 2005 clamav-milter version 0.80j on clamav.icaen.uiowa.edu X-Virus-Scanned: ClamAV 0.80/706/Sun Feb 13 18:14:02 2005, clamav-milter version 0.75 on clamav.icaen.uiowa.edu X-Virus-Status: Clean X-Virus-Status: Clean X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/343 X-Sequence-Number: 10672 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8765F6D17C216B1B0F2EE386 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit John Allgood wrote: > Here is a summary about the cluster suite from redhat. All 9 databases > will be on the primary server the secondary server I have is the > failover. They don't actually share the partitions at the same time. > When you have some type of failure the backup server takes over. Once > you setup the hardware and install the clustering software. You then > setup a service "ie postgres" and then you tell it what harddrive you > will be using. /dev/sde1 and the clustering software takes care of > starting and stopping the postgres database. > Okay, I misunderstood your hardware. So you actually only have 1 machine, with a second machine as a potential rollover. But all transactions occur on the same hardware, even if is a separate "database". I was thinking these were alternate machines. So my first question is why are you partitioning into a separate database, and then updating the master one at night. Since everything is restricted to the same machine, why not just have everything performed on the master? However, sticking with your arrangement, it would seem that you might be able to get some extra performance if each database is on it's own raid, since you are fairly likely to have 2 transactions occuring at the same time, that don't affect eachother (since you wouldn't have any foreign keys, etc on 2 separate databases.) But I think the basic OS RAID1, pg_xlog RAID10, database RAID10 is still a good separation of disks. And probably would help you maximize your throughput. I can't say too much about how the Cluster failover stuff will work with postgres. But as long as one is completely shutdown before the next is started, and they are both running binary compatible versions of postgres, it seems like it would be fine. Not much different from having a second machine that is sitting turned off, which you turn on when the first one fails. John =:-> --------------enig8765F6D17C216B1B0F2EE386 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCHO9EJdeBCYSNAAMRAuhwAJsGL4kbAQN6v97zlAkkJqfS+2WC7gCgho1v 14X8PeioYG/8NsQ9qHTOBIg= =oQhb -----END PGP SIGNATURE----- --------------enig8765F6D17C216B1B0F2EE386--