From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
---|---|
To: | mjnf(at)uevora(dot)pt |
Cc: | "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-17 01:48:51 |
Message-ID: | 37B8BF83.1B7C2043@krs.ru |
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?
In 6.5.X LOCK TABLE without any option (without IN ... MODE)
does the same things as in prev versions: it stops _any_
(both read and write) concurrent access to locked table.
It's bad for performance of read-only transactions -
I would recommend to use LOCK TABLE IN EXCLUSIVE MODE
to block write access (insert/update/delete/select_for_update)
in update transactions and use SERIALIZABLE mode in read-only
ones.
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Serj MD | 1999-08-17 02:04:11 | |
Previous Message | Vadim Mikheev | 1999-08-17 01:33:54 | Re: [GENERAL] v6.5 foreign key trigger reposted with details |