Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id E6EDD2E003D for ; Sun, 15 Jun 2008 14:05:57 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 13847-07 for ; Sun, 15 Jun 2008 14:05:54 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.245]) by developer.postgresql.org (Postfix) with ESMTP id E8B132E003C for ; Sun, 15 Jun 2008 14:05:54 -0300 (ADT) Received: by an-out-0708.google.com with SMTP id d30so1062064and.33 for ; Sun, 15 Jun 2008 10:05:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:reply-to:organization:to :subject:date:user-agent:mime-version:content-type :content-transfer-encoding:content-disposition:message-id:from; bh=xmL9JIwXYhv8I7YMYhQofh279HoC6yyxfYMv+u9MUzo=; b=h76pD5meOawFHKJjCJJMj7BJY78JXaSZVpNEM326FQAuNB4rKD4vkyTpzNF3dI1XDS BSPuYQLdl+Hw+dE7ZJa9RIvMuvDSQHlm7REYA8Zqj2pHpIZNmqwVWtTgL3DBGTV0wD/I C1pBuBZX0BpQOFGS8G5naBXJr1LANMdAOELA0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=reply-to:organization:to:subject:date:user-agent:mime-version :content-type:content-transfer-encoding:content-disposition :message-id:from; b=adzRnG68SuX9Wu/F7iuR4F4tOBaqeUYrnAeP1Xq41tRRtrDXHlbZVaRhlrxsxKL573 fQ0ZlBbAU5FEHf9Eem4AWncEBRkDFwczSHm3ZlsphKdvK9PTDYHxvEI118RgSwmAe9OY Q+LLqC0F2nuF2OaEZz1HKSsd/iuDSaBjYom6E= Received: by 10.101.67.15 with SMTP id u15mr5577926ank.136.1213549554267; Sun, 15 Jun 2008 10:05:54 -0700 (PDT) Received: from ?192.168.0.2? ( [201.245.232.121]) by mx.google.com with ESMTPS id 9sm7994308yws.5.2008.06.15.10.05.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 15 Jun 2008 10:05:53 -0700 (PDT) Reply-To: andreas.philipp@clinicauniversitariateleton.edu.co Organization: =?utf-8?q?Cl=C3=ADnica_Universitaria?= =?utf-8?q?_Telet=C3=B3n?= To: pgsql-admin@postgresql.org Subject: Advice on running two database clusters on one server machine Date: Sun, 15 Jun 2008 12:05:44 -0500 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200806151205.45028.andreas.philipp@clinicauniversitariateleton.edu.co> From: Andreas Philipp X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200806/120 X-Sequence-Number: 29458 Hi all, We are implementing a hospital information system and a human=20 resources/payroll processing system on two identical dedicated servers with= =20 two Xeon Quad Core processors and 32 GB RAM each, both servers being attach= ed=20 via FC to a SAN, and both applications running on PostgreSQL 8.3 / CentOS 5= 1. We are wondering about the advisability to distribute the databases between= =20 the two server machines, both machines acting as active production systems= =20 for one application each, and as warm standby servers for the other, using= =20 WAL shipping to a second database cluster running on another port on each o= f=20 the two server machines. What would be the performance cost of doing so, rather than running all=20 databases on one database cluster on one machine, and using the second=20 machine as a warm standby server for all databases of the two applications? What other considerations should we take into account? We have no prior=20 experience with PostgeSQL administration, having run our previous systems o= n=20 Windows Servers and MS SQL Server. Thanks to all for your input! Andreas Philipp Cl=EDnica Universitaria Telet=F3n Ch=EDa, Colombia