ERROR: tuple concurrently updated

Поиск
Список
Период
Сортировка
От Zubkovsky, Sergey
Тема ERROR: tuple concurrently updated
Дата
Msg-id 528853D3C5ED2C4AA8990B504BA7FB850106DD94@sol.transas.com
обсуждение исходный текст
Ответы Re: ERROR: tuple concurrently updated  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Hello.

=20

Testing of the concurrent access to database objects leaded to the followin=
g error:

=9A

=9A ERROR: tuple concurrently updated

=9A SQL state: XX000

=9A

According to the "PostgreSQL Error Codes" table in the documentation, "XX00=
0" is the PostgreSQL internal error code.

=9A

How to reproduce such an error:=20

=20

1.    Create a table in some database and view:

=20

create table t1 ( id int );

create temp view v1 as select * from t1;

=20

2.    Concurrent access to table t1 is performed by 2 clients (further C1 and =
C2) particularly in this order:

=20

C1: begin; drop view v1;

C2: drop table t1;

C1: commit;

=9A

=9AAnd finally, transaction of the client C2 is terminated with this "expec=
ted" error.

=9A

What's wrong?

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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: "Permission denied" failures occurring on Windows
Следующее
От: Tom Lane
Дата:
Сообщение: Re: ERROR: tuple concurrently updated