Re: Some other odd buildfarm failures
От | Tom Lane |
---|---|
Тема | Re: Some other odd buildfarm failures |
Дата | |
Msg-id | 32318.1419611222@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Some other odd buildfarm failures (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: Some other odd buildfarm failures
|
Список | pgsql-hackers |
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > Tom Lane wrote: >> I've not proven this rigorously, but it seems obvious in hindsight: >> what's happening is that when the object_address test drops everything >> with DROP CASCADE, other processes are sometimes just starting to execute >> the event trigger when the DROP commits. When they go to look up the >> trigger function, they don't find it, leading to "cache lookup failed for >> function". > Hm, maybe we can drop the event trigger explicitely first, then wait a > little bit, then drop the remaining objects with DROP CASCADE? As I said, that's no fix; it just makes the timing harder to hit. Another process could be paused at the critical point for longer than whatever "a little bit" is. regards, tom lane
В списке pgsql-hackers по дате отправления: