pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jodi Kanter <jkanter@virginia.edu>
Cc: Postgres Admin List <pgsql-admin@postgresql.org>
Subject: Re: upgrade?
Date: Mon, 13 May 2002 13:15:55 -0400
Message-ID: <10885.1021310155@sss.pgh.pa.us> (raw)
In-Reply-To: <00e001c1fa8b$fb0a5100$de138f80@virginia.edu>
References: <00e001c1fa8b$fb0a5100$de138f80@virginia.edu>

Jodi Kanter <jkanter@virginia.edu> writes:
> We are still running 7.1.3. Can anyone highlight the big differences or rea=
> sons to upgrade? Is there some documentation on this?

The release notes always mention the main improvements.  Quoting from
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/release.html:


Major changes in this release: 

VACUUM

     Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new VACUUM FULL
     command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. 

Transactions

     There is no longer a problem with installations that exceed four billion transactions. 

OID's

     OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. 

Optimizer

     The system now computes histogram column statistics during ANALYZE, allowing much better optimizer choices. 

Security

     A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket
     authentication option is available on Linux and BSD systems. 

Statistics

     Administrators can use the new table access statistics module to get fine-grained information about table and
     index usage. 

Internationalization

     Program and library messages can now be displayed in several languages. 


			regards, tom lane



view thread (18+ messages)  latest in thread

Message-ID: <10885.1021310155@sss.pgh.pa.us>
Permalink:  ../10885.1021310155@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10885.1021310155@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, jkanter@virginia.edu
  Subject: Re: upgrade?
  In-Reply-To: <10885.1021310155@sss.pgh.pa.us>
  References: <00e001c1fa8b$fb0a5100$de138f80@virginia.edu> <10885.1021310155@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