Vlad,
> It shows only top-level statements. You can see 'select * from f()' in
> this table but you never see what is actually executing in this function.
Queries executed inside functions are opaque to the stats collector for a
variety of technical reasons. Changing this is on the TODO list, b
In response to Vlad Arkhipov :
Is there any way to inspect current running statements (optionally full
stack of these statements)? I've found there is error_context_stack
variable in each backend, but it seems there is no way to get this
variable from another backend. It will be great if P
In response to Vlad Arkhipov :
> Is there any way to inspect current running statements (optionally full
> stack of these statements)? I've found there is error_context_stack
> variable in each backend, but it seems there is no way to get this
> variable from another backend. It will be great if
Is there any way to inspect current running statements (optionally full
stack of these statements)? I've found there is error_context_stack
variable in each backend, but it seems there is no way to get this
variable from another backend. It will be great if Postgres have such
kind of mechanism,
