From: | Jeff Davis <jdavis-pgsql(at)empires(dot)org> |
---|---|
To: | Charl Gerber <charlgerber(at)yahoo(dot)com> |
Cc: | PgSQL General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgre 8.0 vs 7.3 |
Date: | 2005-02-24 18:50:16 |
Message-ID: | 1109271016.4089.51.camel@jeff |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Well, if you're using a feature that's new in 8.0 or new in 7.4, it
certainly won't work on 7.3.
Aside from that, you should be OK. Look at the changelogs for details
though, as 7.3 is a couple releases behind.
For development, however, you normally want the same versions in the
development environment as the production environment.
Regards,
Jeff Davis
On Thu, 2005-02-24 at 13:56 +0000, Charl Gerber wrote:
> Hi,
>
> We have a production environment running postgre 7.3.4
> under linux. We are thinking about setting up a
> windows only development environment, which would mean
> we have to run postgre 8.0 on a windows machine.
>
> Question is, will the code developed under 8.0 run
> without problems under 7.3.4? We're only concerned
> about the actual SQL syntax, SP and trigger
> definitions, FK constraints, etc. Ie, are the syntaxes
> for the two versions the same or what do we need to
> take into consideration here?
>
> Thanks
> Charl
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-02-24 19:41:30 | Re: Postgre 8.0 vs 7.3 |
Previous Message | Craig Bryden | 2005-02-24 18:41:38 | Re: ADO and timestamp/date errors |