| From: | Marcin Inkielman <marn(at)wsisiz(dot)edu(dot)pl> |
|---|---|
| To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
| Cc: | V Krishnaraj <kimi(at)intercept(dot)co(dot)in>, pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] Postgres concurrency : urgent |
| Date: | 1999-11-12 08:35:42 |
| Message-ID: | Pine.LNX.4.04.9911120923570.26188-100000@mi.marnnet |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 12 Nov 1999, Vadim Mikheev wrote:
> > LOCK <<tablename>> IN ACCESS EXCLUSIVE MODE;
> ^^^^^^
> This blocks concurrent read access - is it what you really want?
>
I know it is rather restrictive but when applied to a sequence it inhibits
to a unterminated transaction to change sequence current value (with
for example SELECT nextval('seq')) - ROLLBACK doesn't revert
previous sequence curr. value.
(sorry for my English)
************************************
Marcin Inkielman
************************************
.~.
/V\
// \\
/( )\
^`~'^
powered by Linux
----
sibi omino similis?
************************************
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chairudin Sentosa Harjo | 1999-11-12 09:55:48 | Re: [GENERAL] Postgres concurrency : urgent |
| Previous Message | Vadim Mikheev | 1999-11-12 05:49:10 | Re: Postgres concurrency : urgent |