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 1DF029DC818 for ; Fri, 10 Feb 2006 12:16:21 -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 12494-01 for ; Fri, 10 Feb 2006 12:16:19 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B54E09DC891 for ; Fri, 10 Feb 2006 12:16:18 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1AGGHrx019978; Fri, 10 Feb 2006 11:16:17 -0500 (EST) To: "Given, Robert A" cc: pgsql-admin@postgresql.org Subject: Re: Postgresql performance and tuning questions In-reply-to: <94A24C93CB808844ACB7444B3A188AB4198DF194@XMS.ad2.bu.edu> References: <94A24C93CB808844ACB7444B3A188AB4198DF194@XMS.ad2.bu.edu> Comments: In-reply-to "Given, Robert A" message dated "Fri, 10 Feb 2006 10:36:32 -0500" Date: Fri, 10 Feb 2006 11:16:17 -0500 Message-ID: <19977.1139588177@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.108 required=5 tests=[AWL=0.108] X-Spam-Score: 0.108 X-Spam-Level: X-Archive-Number: 200602/109 X-Sequence-Number: 20530 "Given, Robert A" writes: > Our philosophy is to use products that have been established, tested and > stable. We tend to not go with newer versions until they have time to > mature and have the bugs worked out. This is the version of the DB that > was packaged with the version of Linux we're using. So our thinking is > that we will go with that until we learn better. It is time for you to learn better, right now. 7.4.2 is old and has numerous known bugs. There is a valid argument for sticking to the 7.4.* series, having to do with avoiding any possible application-compatibility issues for apps that've only been tested with 7.4.*, but there is no reason other than vendor laziness to still be on a two-year-old subrelease in the 7.4.* series. 7.4 is currently at 7.4.11 (by Tuesday it will be 7.4.12) and there are a significant number of security holes and risk-of-data-loss bugs fixed in those updates. See the release history at http://developer.postgresql.org/docs/postgres/release.html and then ask yourself if you still trust your Linux vendor's judgment so much. Or you can "learn better" the hard way, by losing data. Your choice. regards, tom lane