Re: simple_heap_update: tuple concurrently updated -- during INSERT
От | SZŰCS Gábor |
---|---|
Тема | Re: simple_heap_update: tuple concurrently updated -- during INSERT |
Дата | |
Msg-id | 00fb01c44efb$594a0ec0$0403a8c0@fejleszt4 обсуждение исходный текст |
Ответ на | simple_heap_update: tuple concurrently updated -- during INSERT ("SZŰCS Gábor" <surrano@mailbox.hu>) |
Список | pgsql-hackers |
Dear Tom, You did it again! The all-amazing-Tom-Lane-clearsight ;) I could reproduce this. I can imagine this practically as: (session 1) someone shutting down one of our Windows clients, while (session 2) another one did the INSERT at the very same moment. This thing caused session 2 to abort. The only thing I still don't understand is the "not in in-progress state" thing. After all, it's the very end of quite a long transaction. Thanks again. I'll lobby to upgrade our production server to 7.4 :) Yours, G. %----------------------- cut here -----------------------% \end ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> Sent: Thursday, June 10, 2004 3:57 PM > session one: > listen foo; > begin; > unlisten foo; > session two: > notify foo; > -- hangs > session one: > end; > -- session two now says > WARNING: AbortTransaction and not in in-progress state > ERROR: simple_heap_update: tuple concurrently updated > > regards, tom lane >
В списке pgsql-hackers по дате отправления: