From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Ian Barwick <barwick(at)gmx(dot)net> |
Cc: | "Dave [Hawk-Systems]" <dave(at)hawk-systems(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: caveats upgrading from 7.0.3 to 7.2.x |
Date: | 2002-11-25 20:36:16 |
Message-ID: | 1038256576.14376.23.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2002-11-22 at 13:21, Ian Barwick wrote:
> On Friday 22 November 2002 18:12, Dave [Hawk-Systems] wrote:
> > am preparing to upgrade the postgres on our servers to 7.2.x from 7.0.3
> >
> > aside from a dump restore requirements and backing up the 7.0.3
> > installation just in case something goes awry, is there anything from a
> > data type or syntax that will cause any major hurdles as a result of this
> > upgrade?
> >
> > Appreciate any forewarnings.
>
> IIRC there aren't any negative syntax changes, i.e. which
> will break something. timestamp() has gone away, and
> SELECT ... LIMIT x,y has been replaced with SELECT ... LIMIT x OFFSET y
> in 7.3.
>
I tested this about 9 months ago, and the timestamp syntax was an issue
(due to changes in how timezones were referenced) so you'll want to
check that. I also remember some issues we had because our lead C
developer had created some functions that generated invalid sql
statements that we're accepted in 7.0.x but rejected on 7.2.x, so you'll
need to check your application for issues like that that might crop up.
I might suggest you take a look at 7.3 which, while currently in beta,
will be released within a fortnight.
Robert Treat
From | Date | Subject | |
---|---|---|---|
Next Message | Medi Montaseri | 2002-11-25 21:44:53 | Re: EXECUTE problems |
Previous Message | Mike Mascari | 2002-11-25 20:28:43 | Re: How To Get Numetic Value!!! using C ??? |