| From: | Chairudin Sentosa Harjo <chai(at)prima(dot)net(dot)id> |
|---|---|
| To: | Marcin Inkielman <marn(at)wsisiz(dot)edu(dot)pl> |
| Cc: | Vadim Mikheev <vadim(at)krs(dot)ru>, 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 09:55:48 |
| Message-ID: | 382BE424.9F658F72@prima.net.id |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Marcin Inkielman wrote:
>
> 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.
How do I lock a sequence?
I must be able to rollback to previous sequence curr.value, if the
transaction fails to work.
I have been looking this for ages, it seems I haven't found the answer
yet.
Regards,
Chai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrzej Mazurkiewicz | 1999-11-12 10:06:33 | RE: [GENERAL] Types available |
| Previous Message | Marcin Inkielman | 1999-11-12 08:35:42 | Re: [GENERAL] Postgres concurrency : urgent |