Re: Locking & concurrency - best practices

Поиск
Список
Период
Сортировка
От Scott Marlowe
Тема Re: Locking & concurrency - best practices
Дата
Msg-id dcc563d10801141315p2374d78fo1e5c0b617cb646cd@mail.gmail.com
обсуждение исходный текст
Ответ на Locking & concurrency - best practices  (Adam Rich <adam.r@indigodynamic.com>)
Ответы Re: Locking & concurrency - best practices  ("Adam Rich" <adam.r@indigodynamic.com>)
Список pgsql-general
On Jan 14, 2008 2:43 PM, Adam Rich <adam.r@indigodynamic.com> wrote:
>
> I have a "parent_tbl" and dozens of data tables, with foreign keys
> referencing the PK of "parent_tbl" (one-to-many).  There are 100+
> users accessing the application, usually (but not always) each user
> is working on a different record in parent_tbl.  (this would seem like
> a pretty standard scenario for a lot of apps)

You should be able to do "select for update" on both parent and child
records and get the effect you desire.

Think up your own worst case scenario for concurrent updates, then sit
down at two or more psql terminals, and try to simulate such a thing
and see what happens.  Experimentation is a great tool.

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

Предыдущее
От: "Gurjeet Singh"
Дата:
Сообщение: Re: Forgot to dump old data before re-installing machine
Следующее
От: "Adam Rich"
Дата:
Сообщение: Re: Locking & concurrency - best practices