Re: No Timeout in SELECT..FOR UPDATE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Anthony Rich <richae(at)optusnet(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: No Timeout in SELECT..FOR UPDATE
Date: 2004-02-15 21:36:28
Message-ID: 10784.1076880988@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Anthony Rich <richae(at)optusnet(dot)com(dot)au> writes:
> When one process has a "row lock" on one or more rows
> in a table, using "SELECT...FOR UPDATE" in default lock
> mode, another process has NO WAY of aborting from the
> same request, and reporting to the user that this record
> is already locked, reserved, or whatever you want to call it.

Not so. See the statement_timeout parameter.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2004-02-15 21:48:12 Re: No Timeout in SELECT..FOR UPDATE
Previous Message Hans-Jürgen Schönig 2004-02-15 21:15:50 Re: No Timeout in SELECT..FOR UPDATE