pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Given, Robert A <bgiven@bu.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgresql performance and tuning questions
Date: Fri, 10 Feb 2006 11:16:17 -0500
Message-ID: <19977.1139588177@sss.pgh.pa.us> (raw)
In-Reply-To: <94A24C93CB808844ACB7444B3A188AB4198DF194@XMS.ad2.bu.edu>
References: <94A24C93CB808844ACB7444B3A188AB4198DF194@XMS.ad2.bu.edu>

"Given, Robert A" <bgiven@bu.edu> 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



view thread (10+ messages)  latest in thread

Message-ID: <19977.1139588177@sss.pgh.pa.us>
Permalink:  ../19977.1139588177@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19977.1139588177@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, bgiven@bu.edu
  Subject: Re: Postgresql performance and tuning questions
  In-Reply-To: <19977.1139588177@sss.pgh.pa.us>
  References: <94A24C93CB808844ACB7444B3A188AB4198DF194@XMS.ad2.bu.edu> <19977.1139588177@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox