Re: Lock record
| От | Andrew Sullivan |
|---|---|
| Тема | Re: Lock record |
| Дата | |
| Msg-id | 20000615143827.G1021@bpl.on.ca обсуждение исходный текст |
| Ответ на | Re: Lock record (Jurgen Defurne <defurnj@glo.be>) |
| Список | pgsql-general |
On Thu, Jun 15, 2000 at 08:08:50PM +0200, Jurgen Defurne wrote:
> Then user A inhibits user B from going further until transaction A has been
> completed. If this person goes for a coffee, then transaction B will also be
> held
> up indefinitely.
[. . .]
>
> of the needed data. Further functionality of locks included always the
> possibility
> of specifying a time-out and getting the name of the user who currently holds
> the lock.
In my pg_options file, I have the ability to time out deadlocks like you
describe. The file should be located at $PGDATA/pg_options. See below:
# deadlock timeout; set this to a non-zero integer, which is the number
# of seconds that the backend should wait before deciding that it is in
# a deadlock and timing out. The system default is 1 second.
deadlock_timeout = [insert your value here]
--
Andrew Sullivan Computer Services
<sullivana@bpl.on.ca> Burlington Public Library
+1 905 639 3611 x158 2331 New Street
Burlington, Ontario, Canada L7R 1J4
В списке pgsql-general по дате отправления: