Re: SELECT FOR UPDATE NOWAIT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Paulo Scardine" <paulos(at)cimed(dot)ind(dot)br>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SELECT FOR UPDATE NOWAIT
Date: 2003-07-23 19:06:38
Message-ID: 15579.1058987198@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Paulo Scardine" <paulos(at)cimed(dot)ind(dot)br> writes:
> - Where is the best place to put this?

I think it would be a really *bad* idea to put it in LockAcquire; that
risks breaking things that you don't want broken.

Whether it's special syntax or a GUC variable, the restriction should
only apply to SELECT FOR UPDATE row locks, perhaps user-commanded LOCK
TABLE operations, and maybe one or two other places that are known to
be used only for user-written operations and not for system-initiated
ones. Those places would need to check whether to do a conditional
or unconditional lock.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jenny - 2003-07-23 19:27:02 how do i turn off the html tags??
Previous Message Jenny - 2003-07-23 19:01:15