On Thu, Jun 25, 2026 at 6:33 AM Andrei Lepikhov <[email protected]> wrote: > Ok, so just mention this behaviour in the documentation - let people know that > they should potentially wait for a minute or two more to see the EXPLAIN. > Real-life with huge queries and big machines provide us with examples where a > backend might delay a response to a signal for quite a substantial time. > > Sometimes nothing happens after such an async operation, and we need to > identify > the problem: has the backend stalled, is the ‘logging plan’ algorithm > ineffective, or is something else happening?
I don't think we document this in other, similar cases. Many things can be delayed if the machine is overloaded, but unless I am missing something, having to wait over a minute for this to work would be *extremely* unusual and only happen in case of a machine that is absolutely being crushed by the load. And in that case everything else will be slow, too. -- Robert Haas EDB: http://www.enterprisedb.com
