Re: SELECT FOR UPDATE NOWAIT

From: "Paulo Scardine" <paulos(at)cimed(dot)ind(dot)br>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SELECT FOR UPDATE NOWAIT
Date: 2003-07-23 18:57:17
Message-ID: 014401c3514c$3c915e30$63000a0a@cimed.ind.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> My guess is that we will implement it was a SET variable so it can
> control FOR UPDATE/LOCK/UPDATE/DELETE.
>
> Added to TODO:
>
> Add GUC variable to prevent waiting on locks

Interesting.

I have a lot of potentially dumb questions:
- Is this easier to implement as a user variable than in the parser or is
some kind of police (SQL compliance, etc.)?
- These locks are grant by LockAcquire() or by higher level functions?
- Where is the best place to put this?

TIA,
--
Paulo Scardine

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com)
Version: 6.0.490 / Virus Database: 289 - Release Date: 16/6/2003

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jenny - 2003-07-23 19:01:15
Previous Message Bruce Momjian 2003-07-23 18:16:42 Re: SELECT FOR UPDATE NOWAIT