pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kris Deugau <kdeugau@vianet.ca>
To: pgsql-admin@postgresql.org
Subject: Re: Actual expression of a constraint
Date: Wed, 08 Feb 2006 10:52:22 -0500
Message-ID: <43EA13B6.6050403@vianet.ca> (raw)
In-Reply-To: <43E9C995.4060904@aircomp.aero>
References: <43E71F51.7030108@aircomp.aero>
	<27878.1139249149@sss.pgh.pa.us>
	<43E8BDE3.6000802@aircomp.aero>
	<7508.1139328081@sss.pgh.pa.us>
	<43E8D024.40900@aircomp.aero>
	<27461.1139336188@sss.pgh.pa.us>
	<43E9C995.4060904@aircomp.aero>

lrotger wrote:
> I read some of the logs up until 7.3 (from my old 7.2.1); I should 
> benefit from upgrading but there are issues to consider, for example, I 
> see 'timestamp' was changed from with to without time zone in 7.3, I'll 
> have to follow these changes carefully to upgrade without problems.

Tom's major recommendation is to move up to the latest 7.2 release - 
which, while currently unsupported, contains a number of BIG bugfixes 
relating to data integrity.  (IIRC the version number is 7.2.5).  You 
should be able to install packages or build from source and install in 
place without any changes to your code.  Getting a dump of your data 
beforehand is always a good idea Just In Case, but it shouldn't be 
necessary most of the time.

Jumping between "major" versions (eg, 7.2->7.3) is where there are 
changes to data types and the back-end storage;  for a major version 
change the usual recommendation is to dump and reload.

Check back through the list archives;  this general recommendation ("For 
PG version x.x.n, always run the latest point-release (n) for any given 
major version (x.x)") has been posted quite a few times over this past 
year alone.

-kgd



view thread (9+ messages)

Message-ID: <43EA13B6.6050403@vianet.ca>
Permalink:  ../43EA13B6.6050403@vianet.ca/
Also on:    postgresql.org/message-id/43EA13B6.6050403@vianet.ca

 · 

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: kdeugau@vianet.ca
  Subject: Re: Actual expression of a constraint
  In-Reply-To: <43EA13B6.6050403@vianet.ca>
  References: <43E71F51.7030108@aircomp.aero> <27878.1139249149@sss.pgh.pa.us> <43E8BDE3.6000802@aircomp.aero> <7508.1139328081@sss.pgh.pa.us> <43E8D024.40900@aircomp.aero> <27461.1139336188@sss.pgh.pa.us> <43E9C995.4060904@aircomp.aero> <43EA13B6.6050403@vianet.ca>

* 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