From schooleys@co.kern.ca.us Thu Oct 7 23:28:53 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 014EB32A766 for ; Fri, 8 Oct 2004 00:28:53 +0100 (BST) 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 53699-05 for ; Thu, 7 Oct 2004 23:28:49 +0000 (GMT) Received: from kc.co.kern.ca.us (kc.co.kern.ca.us [206.169.45.183]) by svr1.postgresql.org (Postfix) with ESMTP id B7BCE329D8C for ; Fri, 8 Oct 2004 00:28:50 +0100 (BST) Received: from no.name.available by kc.co.kern.ca.us via smtpd (for svr1.postgresql.org [200.46.204.71]) with ESMTP; Thu, 7 Oct 2004 16:30:22 -0700 X-eSCM-MailFrom: Received: from mail.co.kern.ca.us (11.50.27.200) by antispamca.co.kern.ca.us (11.2.48.6); Thu, 07 October 2004 16:27:59 -0700 Received: from KERNMAIL-Message_Server by co.kern.ca.us with Novell_GroupWise; Thu, 07 Oct 2004 16:28:34 -0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.7.1 Date: Thu, 07 Oct 2004 16:28:26 -0700 From: "Sharon Schooley" To: Subject: High Availability for PostgreSQL Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_AF8F8632.B3D2E957" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.8 tagged_above=0.0 required=5.0 tests=HTML_30_40, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200410/142 X-Sequence-Number: 15135 This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_AF8F8632.B3D2E957 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello,=20 We are looking for a 24/7 PostgreSQL solution. I've read some postings and = information on various solutions including Taygeta, pgpool and Mammoth Post= greSQL with Heartbeat. If there are any users of these or other PostgreSQL= high availability solutions out there, can you respond and let me know wha= t is working for you and how long you have been up and running?=20=20 =20 Our project is a high profile but simple application that must run 24/7. W= e are a county government entity. We are not currently PostgreSQL users. Our o/= s is Suse 9.0 Pro Server. Thank you, Sharon Schooley Database Analyst Kern County Information Technology Services 1215 Truxtun Avenue Bakersfield, CA 93301 (661) 868-2263 --=_AF8F8632.B3D2E957 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML
Hello,
 
We are looking for a 24/7 PostgreSQL solution. I've read some postings= and=20 information on various solutions including Taygeta, pgpool and Mammoth=20 PostgreSQL with Heartbeat.  If there are any users of these or other= =20 PostgreSQL high availability solutions out there, can you respond and let m= e=20 know what is working for you and how long you have been up and=20 running? 
 
Our project is a high profile but simple=20 application that must run 24/7.  We are
a county government=20 entity.  We are not currently PostgreSQL users.  Our o/s is
Su= se=20 9.0 Pro Server.
 
Thank you,

Sharon Schooley
Database= =20 Analyst
Kern County Information Technology=20 Services
1215 Truxtun= =20 Avenue
Bakersfield, CA= =20 93301
(661)=20 868-2263

 
--=_AF8F8632.B3D2E957-- From schooleys@co.kern.ca.us Fri Oct 8 18:16:55 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DD73832A0CB for ; Fri, 8 Oct 2004 19:16:55 +0100 (BST) 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 11318-08 for ; Fri, 8 Oct 2004 18:16:18 +0000 (GMT) Received: from kc.co.kern.ca.us (kc.co.kern.ca.us [206.169.45.183]) by svr1.postgresql.org (Postfix) with ESMTP id 62671329FBB for ; Fri, 8 Oct 2004 19:16:14 +0100 (BST) Received: from no.name.available by kc.co.kern.ca.us via smtpd (for svr1.postgresql.org [200.46.204.71]) with ESMTP; Fri, 8 Oct 2004 11:17:49 -0700 X-eSCM-MailFrom: Received: from mail.co.kern.ca.us (11.50.27.200) by antispamca.co.kern.ca.us (11.2.48.6); Fri, 08 October 2004 11:15:33 -0700 Received: from KERNMAIL-Message_Server by co.kern.ca.us with Novell_GroupWise; Fri, 08 Oct 2004 11:16:07 -0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.7.1 Date: Fri, 08 Oct 2004 11:15:48 -0700 From: "Sharon Schooley" To: < > Subject: High Availability for PostgreSQL Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_E1C1CB77.4B2A1E70" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=4.3 tagged_above=0.0 required=5.0 tests=HTML_30_40, HTML_MESSAGE, NO_DNS_FOR_FROM, TO_HAS_SPACES X-Spam-Level: **** X-Archive-Number: 200410/133 X-Sequence-Number: 15126 This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_E1C1CB77.4B2A1E70 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello,=20 We are looking for a 24/7 PostgreSQL solution. I've read some postings and = information on various solutions including Taygeta, pgpool, and Mammoth Pos= tgreSQL with Heartbeat. If there are any users of these or other PostgreSQ= L high availability solutions out there, can you respond and let me know wh= at is working for you and how long you have been up and running?=20=20 =20 Our project is a high profile but simple application that must run 24/7. W= e are a county government entity. We are not currently PostgreSQL users. = Our o/s is Suse 9.0 Pro Server. Thank you, Sharon Schooley Database Analyst Kern County Information Technology Services 1215 Truxtun Avenue Bakersfield, CA 93301 (661) 868-2263 --=_E1C1CB77.4B2A1E70 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML
Hello,
 
We are looking for a 24/7 PostgreSQL solution. I've read some postings= and=20 information on various solutions including Taygeta, pgpool, and Mammoth=20 PostgreSQL with Heartbeat.  If there are any users of these or other= =20 PostgreSQL high availability solutions out there, can you respond and let m= e=20 know what is working for you and how long you have been up and=20 running? 
 
Our project is a high profile but simple=20 application that must run 24/7.  We are a county government entity.&nb= sp;=20 We are not currently PostgreSQL users.  Our o/s is
Suse 9.0 Pro=20 Server.
 
Thank you,

Sharon Schooley
Database= =20 Analyst
Kern County Information Technology=20 Services
1215 Truxtun= =20 Avenue
Bakersfield, CA= =20 93301
(661)=20 868-2263

 
--=_E1C1CB77.4B2A1E70-- From cbbrowne@acm.org Fri Oct 8 23:20:06 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C0341329FDB for ; Sat, 9 Oct 2004 00:20:06 +0100 (BST) 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 94595-08 for ; Fri, 8 Oct 2004 23:19:54 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 619BA329EE1 for ; Sat, 9 Oct 2004 00:19:54 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i98NJo2B096850 for ; Fri, 8 Oct 2004 23:19:50 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i98Mo2jk090557 for pgsql-admin@postgresql.org; Fri, 8 Oct 2004 22:50:02 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.admin Subject: Re: High Availability for PostgreSQL Date: Fri, 08 Oct 2004 18:34:26 -0400 Organization: cbbrowne Computing Inc Lines: 62 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:6LB2kv81+TxJGgwg1BrWCk674G4= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/137 X-Sequence-Number: 15130 Centuries ago, Nostradamus foresaw when schooleys@co.kern.ca.us ("Sharon Schooley") would write: > We are looking for a 24/7 PostgreSQL solution. I've read some > postings and information on various solutions including Taygeta, > pgpool, and Mammoth PostgreSQL with Heartbeat.  If there are any > users of these or other PostgreSQL high availability solutions out > there, can you respond and let me know what is working for you and > how long you have been up and running?    Our project is a high > profile but simple application that must run 24/7.  We are a county > government entity.  We are not currently PostgreSQL users.  Our o/s > is Suse 9.0 Pro Server. The issues likely have more to do with what kind of hardware you are running than the software. To build an HA system generally requires looking at _all_ the pieces, to make sure they fit together well, including: - The database itself - Middleware - Hardware, including such things as: - Redundant servers - Servers containing redundant hardware (e.g. - extra CPUs, memory boards) - Network appliances - Applications using the stuff in the lower layers Sometimes the middleware can hide hardware outages while backup hardware "spins up"; if the applications are designed to be either more or less forgiving of outages, that can either help or hurt. Running a demanding application 168h/week on a set of hardware infrastructure not designed for that will leave considerable risk of embarrassing failures. We've got people looking into AIX+HACMP for some applications; one thing we discovered is that this (expensive) technology is likely to make system reliability MUCH WORSE if it is not used properly. What you'll need (similar to the HACMP efforts) is to have the time to test your systems well under considerable load in order to figure out what are the "sharp edges" so that the system 'bleeds' a little in QA, but runs well in production. There will always be some of this, whatever set of technologies you pick for any complex project. There's always some unexpected local lessons to learn. After we ran the Slony-I replication system for about a week, we determined that it was _vital_ to do regular maintenance ("vacuuming") on the internal table "pg_listener" otherwise system performance would steadily get pretty bad. Your application will have different patterns, but there will be some [likely small] set of vital bottlenecks, hard to discover until it is under load. Changing technologies will merely change which bottlenecks you hit :-). -- (reverse (concatenate 'string "moc.liamg" "@" "enworbbc")) http://www.ntlug.org/~cbbrowne/unix.html There's a new language called C+++. The only problem is every time you try to compile your modem disconnects. From peter_e@gmx.net Mon Oct 11 10:22:06 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2996732A301 for ; Mon, 11 Oct 2004 11:22:06 +0100 (BST) 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 51260-07 for ; Mon, 11 Oct 2004 10:21:56 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by svr1.postgresql.org (Postfix) with SMTP id 14C3932A918 for ; Mon, 11 Oct 2004 11:21:57 +0100 (BST) Received: (qmail 19290 invoked by uid 65534); 11 Oct 2004 10:21:56 -0000 Received: from dsl-082-082-234-194.arcor-ip.net (EHLO colt.pezone.net) (82.82.234.194) by mail.gmx.net (mp026) with SMTP; 11 Oct 2004 12:21:56 +0200 X-Authenticated: #495269 From: Peter Eisentraut To: "Sharon Schooley" , Subject: Re: High Availability for PostgreSQL Date: Mon, 11 Oct 2004 12:21:55 +0200 User-Agent: KMail/1.5.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410111221.55823.peter_e@gmx.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/155 X-Sequence-Number: 15148 Sharon Schooley wrote: > We are looking for a 24/7 PostgreSQL solution. I've read some > postings and information on various solutions including Taygeta, > pgpool and Mammoth PostgreSQL with Heartbeat. If there are any users > of these or other PostgreSQL high availability solutions out there, > can you respond and let me know what is working for you and how long > you have been up and running? We use shared storage and heartbeat, or DRBD and heartbeat. We have several installations have have been running for at least a year. It's easy to set up, low maintenance, and it works. -- Peter Eisentraut http://developer.postgresql.org/~petere/