From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jarednevans(at)yahoo(dot)com (Jared Evans) |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 7.2 or 7.4 for critical data? |
Date: | 2004-05-07 00:52:28 |
Message-ID: | 26630.1083891148@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
jarednevans(at)yahoo(dot)com (Jared Evans) writes:
> I will be installing Debian distro soon at my company. I'll be
> storing critical data and am wondering if I should go with stable 7.2
> version or use the 7.4 version (for all the latest features and bug
> fixes). I'm currently doing the research for the management here.
7.2 is not "stable", it's "obsolete". We stopped fixing bugs in it
quite some time ago. I would consider it less reliable than either
7.3.6 or 7.4.2, because it hasn't gotten the benefit of fixes for any
bugs discovered in the last year or more. By and large we do tend to
fix more bugs than we introduce with each new release ;-).
My recommendation would be to go with 7.4.2 (or later). You could also
make a case for 7.3.6 but really I think that that's pointless for a new
installation. The only good reason to be installing 7.3.6 at this point
is if you've got an existing database you can't afford to initdb, or if
you've got serious compatibility problems with updating an existing
application to 7.4.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-07 01:02:21 | Re: CHECK constraints and optimizations |
Previous Message | Karsten Hilbert | 2004-05-07 00:33:04 | Re: Verhindern, dass im Mehrbenutzerbetrieb mit veralteten Daten gearbteitet wird |