On Fri, 2006-02-10 at 09:36, Given, Robert A wrote:
> 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. Our experience is more
> with mainframes where habitually we proceed methodically. (That
> translates to: slower than what we see with open source.)
>
> Is there an impelling reason why we should migrate to a newer version
> before we begin to use, observe, and experience Postgres of our own?
But you're not running the least buggy version of the 7.4 branch. The
7.4 branch is up to 7.4.9. If you are runing 7.4.2 then you haven't
installed all the updates supplied by Suse for their distribution (or
Suse backports bug fixes from 7.4.9 to 7.4.2, which I kinda doubt) which
means you likely haven't upgraded ANY of the packages that came with it,
which means your system, if it is put on the internet, will likely be
hacked within days, if not hours.
I would recommend looking into at least 8.0. It's been out for a year,
it's quite stable, and has many features like point in time recovery
that make it a very good choice for production.
> Thanks, Bob
>
>
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Friday, February 10, 2006 10:16 AM
> To: Given, Robert A
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Postgresql performance and tuning questions
>
> "Given, Robert A" <bgiven@bu.edu> writes:
> > We are beginning a project to use Postgresql 7.4.2 on zLinux SLES9 The
>
> > application of interest is uPortal 2.4.3.
>
> Why are you not starting with a reasonably up-to-date version of
> Postgres?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend