Re: Patch for LISTEN/NOTIFY race condition?
От | Meetesh Karia |
---|---|
Тема | Re: Patch for LISTEN/NOTIFY race condition? |
Дата | |
Msg-id | 480EED8A.9040904@gmail.com обсуждение исходный текст |
Ответ на | Re: Patch for LISTEN/NOTIFY race condition? (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
Thanks all ... I'm going to do some more digging and see if I can isolate the problem. Meetesh Tom Lane wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: > >> Meetesh Karia wrote: >> >>> After upgrading to 8.3 and Slony 1.2.13, one of our import processes >>> started constantly failing because of deadlock. Our import process >>> (pl/pgsql function) just uses COPY FROM to populate a temp table and >>> then inserts from that (without any special locks, etc). And, the >>> deadlock error showed that the import process was waiting on sl_event >>> and a slon process was waiting on pg_listener. >>> >>> I found the following thread in the archives: >>> http://archives.postgresql.org/pgsql-bugs/2008-03/msg00117.php and it >>> seemed like it could be the cause of the problem. >>> >>> Is the patch available anywhere? Also, if it will be available in >>> 8.3.2, is there any information on when that will be released? >>> > > >> Hmm, AFAICS the patch should be present on 8.3.1, because it was tagged >> on March 14th and the patch was committed on March 12. >> > > Yes, but in any case (a) that's about a race condition not a deadlock, > and (b) the issue has been there since forever, so it is unlikely to > explain or fix a problem that you weren't seeing before 8.3. > > regards, tom lane >
В списке pgsql-bugs по дате отправления: