X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 940369DC9D7 for ; Tue, 7 Feb 2006 19:09:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72913-04 for ; Tue, 7 Feb 2006 19:09:36 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.193]) by postgresql.org (Postfix) with ESMTP id 2A7309DC803 for ; Tue, 7 Feb 2006 19:09:31 -0400 (AST) Received: by xproxy.gmail.com with SMTP id i30so1037170wxd for ; Tue, 07 Feb 2006 15:09:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=W41/Q8oFJyxso/fAXaIYlnYwV6RwVNkYqSRaTGo1pI9IpTaa9ANOETfTirCh4WR1asjQ4mcKN0PP0d/7rD3Pq8Ba3BwtbrZ7uc1Rgrbi715hGCznGpik59eDxnr/of2xOy65yiSXo1aEPxU4uDSSrhfbI6tG8Z3ebzdYDb2whVM= Received: by 10.70.118.19 with SMTP id q19mr6387963wxc; Tue, 07 Feb 2006 15:09:34 -0800 (PST) Received: by 10.70.70.7 with HTTP; Tue, 7 Feb 2006 15:09:34 -0800 (PST) Message-ID: Date: Tue, 7 Feb 2006 18:09:34 -0500 From: Colin Freas To: pgsql-admin@postgresql.org Subject: Postgresql 8.0 or 8.1 vs. latest Red Hat RPM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25127_25035333.1139353774786" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.643 required=5 tests=[HTML_00_10=0.642, HTML_MESSAGE=0.001] X-Spam-Score: 0.643 X-Spam-Level: X-Archive-Number: 200602/75 X-Sequence-Number: 20496 ------=_Part_25127_25035333.1139353774786 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm in the midst of a knock-down-drag-out with a sysadmin (who, somewhat unfortunately, is also a good friend) over how to administer Postgresql on some new machines we've got in. My argument is we should use the latest stable version of Postgres. His take is we ought to use the latest version provided by Red Hat. (This is for a set of Red Hat Enterprise boxes.) Normally, I'd just say do what you want in production, I'll do what I want in development, and we'll settle the differences in committee. But, since we've finally got perfectly mirrored hardware, we'd like to see the same in software. Any particularly compelling arguments or points would be valuable, either way. One point of contention in this argument seems to be the notion that Red Ha= t ports security fixes to older versions, even if it has to do this itself. = I don't necessarily believe that this happens. That is, imagine that there's some fix that makes it into the 8.x branch. For whatever reason, this doesn't go into 7.x. Red Hat is still using the 7.x branch, so it undertakes to do this work itself. Does that sort of thing really happen? Is there a general performance improvement from 7 to 8? What about reliability improvements? For how long is the 7.x branch going to be under maintenance and developmen= t (by the community, not be Red Hat)? Is there even a time frame? Again, any thoughts appreciated. Thanks, Colin ------=_Part_25127_25035333.1139353774786 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I'm in the midst of a knock-down-drag-out with a sysadmin (who, somewha= t unfortunately, is also a good friend) over how to administer Postgresql o= n some new machines we've got in.

My argument is we should use the l= atest stable version of Postgres.  His take is we ought to use the lat= est version provided by Red Hat.  (This is for a set of Red Hat Enterp= rise boxes.)

Normally, I'd just say do what you want in production, I'll do what= I want in development, and we'll settle the differences in committee. = ; But, since we've finally got perfectly mirrored hardware, we'd like to se= e the same in software.

Any particularly compelling arguments or points would be valuable, = either way.

One point of contention in this argument seems to be the= notion that Red Hat ports security fixes to older versions, even if it has= to do this itself.  I don't necessarily believe that this happens.&nb= sp; That is, imagine that there's some fix that makes it into the=20 8.x branch.  For whatever reason, this doesn't go into 7.x.  Red = Hat is still using the 7.x branch, so it undertakes to do this work itself.=   Does that sort of thing really happen?

Is there a general per= formance improvement from 7 to 8?  What about reliability improvements= ? =20

For how long is the 7.x branch going to be under maintenance and de= velopment (by the community, not be Red Hat)?  Is there even a time fr= ame?

Again, any thoughts appreciated.

Thanks,
Colin
------=_Part_25127_25035333.1139353774786--