From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ToDo: log plans of cancelled queries |
Date: | 2013-01-11 16:31:59 |
Message-ID: | CAFj8pRDKPEiwY0EBKyeTpTEe=VjCTF5Q_WpM-f+JutuWyCJU0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/1/11 Stephen Frost <sfrost(at)snowman(dot)net>:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> > An even better feature would be to be able to send a signal to a
>> > running query to log its currently executing plan. That way you can
>> > ask "Why so slow?" before deciding to kill it.
>>
>> That could conceivably work. At least it wouldn't require running
>> EXPLAIN in a failed transaction.
>
> I like this idea, in general, also. Taking that to the next level would
> be figuring out how you can do the same kind of thing through an
> interactive psql session where the user running the query doesn't need
> access to the database server or PG log files...
>
this is simple - it can be printed via elog(WARNING, ...) to original console
> We can send a 'cancel query', how about a 'report on query' which
> returns the plan and perhaps whatever other stats are easily available?
there is only one question - that POSIX signal we can use?
Pavel
>
> Thanks,
>
> Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2013-01-11 16:33:55 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
Previous Message | Andres Freund | 2013-01-11 16:31:13 | Re: foreign key locks |