From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Some other odd buildfarm failures |
Date: | 2014-12-26 16:27:02 |
Message-ID: | 32318.1419611222@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-12-26 16:35:46 | Re: Some other odd buildfarm failures |
Previous Message | Alvaro Herrera | 2014-12-26 16:24:00 | Re: Some other odd buildfarm failures |