Re: Concurrency

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Concurrency
Дата
Msg-id 1115665123.3830.38.camel@localhost.localdomain
обсуждение исходный текст
Ответ на Concurrency  (Kris Kiger <kris@musicrebellion.com>)
Ответы Re: Concurrency  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-admin
On Mon, 2005-05-09 at 12:21 -0500, Kris Kiger wrote:
> Quick question.  I lock a table, call it table X, and then issue two
> updates on that table.  The two updates are left waiting.  I then unlock
> the table.   The two updates go through.  My question is, is there a
> predictable way to determine which query will be executed first?  Thanks
> in advance

The lock queue is served in FIFO sequence. It is predictable, but if you
don't know which order they were submitted in it might be hard to
determine what that predictable order is, if they were submitted almost
at the same time.

...but you shouldn't use locking as a queuing mechanism.

Best Regards, Simon Riggs


В списке pgsql-admin по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: conversion security update may have slowed our system?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: conversion security update may have slowed our system?