Issues w/ 7.1 to 7.2 upgrade. - Mailing list pgsql-sql

From Diehl, Jeffrey
Subject Issues w/ 7.1 to 7.2 upgrade.
Date
Msg-id B51F0C636E578A4E832D3958690CD73E0130C20A@es04snlnt
Whole thread Raw
Responses Re: Issues w/ 7.1 to 7.2 upgrade.
Re: Issues w/ 7.1 to 7.2 upgrade.
List pgsql-sql
Hi all.

I just upgraded from 7.1 to 7.2, mainly because of the facts that vacuum
doesn't do table locks and I thought that "replace into" would be in 7.2.

Anyway, I don't see that "replace into" is there...

Also, I noticed a slight difference that caught me off guard:

If I try to insert '1234567890' into a varchar(5) under 7.1, the value of
the field will be '12345'.

If I try it under 7.2, I get an error.

Needless to say, I learned a bit more about my dataset this morning...
<grin>

Mike Diehl,
Network Monitoring Tool Devl.
Sandia National Laboratories.
(505) 284-3137
jdiehl@sandia.gov



pgsql-sql by date:

Previous
From: Benoit Menendez
Date:
Subject: Re: Problem with self-join updates...
Next
From: Mark Stosberg
Date:
Subject: CURRENT_TIMESTAMP breaking with 7.1->7.2 dump/import