Re: Postgresql takes more time to update

Hi Peter,

Thanks for your reply and to your colleague Scott. Can you pls explain
below sentence marked in red.

- --------- ------------------ ---------------------

As an alternative to Scott's suggestion (upgrading to the newest 7.4),
you could update your postgresql installation to 8.2, or if you can wait
a few months, 8.3. There are *huge* performance gains (I recently made a
similar switch and everything is blazing fast). Please note that this
will require a dump/restore of the data and more involved testing, so
only do it if you can devote the time, money, and energy.

- --------- ---------------- ------------- --------------

Is 8.2 version is not free downloadable? What type of testing is
required? Pls advice us.

with thanks and regards,

G.V. Suresh Gupta

Sr. Software Engineer

Batelco Phase II

Mo: +91 9890898688

Ph : +9120 66453213

________________________________

From: Peter Koczan [mailto:pjkoczan(at)gmail(dot)com]
Sent: Saturday, October 06, 2007 11:00 PM
To: Suresh Gupta VG
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Postgresql takes more time to update

We are using "psql 7.4.2" version of Postgresql, these days all
the transactions on the database are taking long time to execute. We are
planning to do "ANALYZE " command on the database. Could you please
advice us, how much time it takes and what are the conditions we need to
keep on an eye.

As an alternative to Scott's suggestion (upgrading to the newest 7.4),
you could update your postgresql installation to 8.2, or if you can wait
a few months, 8.3. There are *huge* performance gains (I recently made a
similar switch and everything is blazing fast). Please note that this
will require a dump/restore of the data and more involved testing, so
only do it if you can devote the time, money, and energy.

As far as analyze goes, you should be running ANALYZE VERBOSE, or better
yet, VACUUM ANALYZE VERBOSE (see
http://www.postgresql.org/docs/7.4/interactive/sql-vacuum.html ) so you
can interpret the output. The vacuum also helps manage disk space, and
this isn't a big performance hit because it doesn't require exclusive
locks (though a VACUUM FULL would, again, read the docs). In fact, you
should be doing this regularly, daily if possible.

For me, I have a 30 GB database cluster, and vacuum/analyze takes about
3 minutes, though YMMV. You want to look for output regarding FSM pages
and relations and adjust as necessary (otherwise you're running into
index bloat).

Can you please tell us whether we had any other commands are
available on postgresql to increase the performance of the database and
database tools available for Postgresql on Solaris sparc machine?

I think Scott covered all of this. Alternatively, you could look to
upgrading your hardware (multi-core x86 hardware is very nice), but
without knowing your needs, usage, or budget, I can't make that
determination.

Hope this helps.

Peter

DISCLAIMER:
This email may contain confidential or privileged information for the intended recipient(s) and the views expressed in the same are not necessarily the views of Zensar Technologies Ltd. If you are not the intended recipient or have received this e-mail by error, its use is strictly prohibited, please delete the e-mail and notify the sender. Zensar Technologies Ltd. does not accept any liability for virus infected mails.