From: | Mario Jorge Nunes Filipe <mjnf(at)neptuno(dot)sc(dot)uevora(dot)pt> |
---|---|
To: | "pgsql-general(at)postgreSQL(dot)org" <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] moving from 6.3.2 to 6.5 |
Date: | 1999-08-13 11:39:56 |
Message-ID: | 37B4040C.7A660461@neptuno.uevora.pt |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mario Jorge Nunes Filipe wrote:
>
> Hi
>
> I have a relatively large application developed with php and postgres
> using pg 6.3.2. I read the changelog for v.6.5 and i got a little bit
> scared, but maybe i understood things in the wrong way.
>
> In this application every "race condition" is placed in a begin->end
> block and most of them even have lock's before they're needed just mo
> make sure. If I upgrade postgres to 6.5 is there any danger that with
> the new locking mechanism my app's database starts getting corrupted or
> start's giving out the wrong type of information?
Ok! Mea culpa. I probably didn't read the RELEASE file but i just saw a
message from someone with a similar problem.
So, correct me if i'm wrong, as long as i use LOCK's i won't be running
into trouble, right ?
BTW, do i have to install 6.4 to pass from 6.3 to 6.5?
P.S : I'm not thinking about upgrading the production server yetm just
the devel one...
--
Mario Filipe
mjnf(at)uevora(dot)pt
http://neptuno.sc.uevora.pt/~mjnf
From | Date | Subject | |
---|---|---|---|
Next Message | amy cheng | 1999-08-13 12:07:34 | how perl get trigger info? |
Previous Message | Mario Jorge Nunes Filipe | 1999-08-13 11:25:27 | moving from 6.3.2 to 6.5 |