Indeed, the query log is updated at the end of the query. Storing it also at the beginning in query table is a feature to be considered for the future. On 6/15/12 7:35 PM, Fabian Groffen wrote:
On 15-06-2012 19:30:51 +0200, Stefan de Konink wrote:
On 15-06-12 19:26, Fabian Groffen wrote:
On 15-06-2012 19:21:09 +0200, Stefan de Konink wrote:
On 15-06-12 17:58, Fabian Groffen wrote:
On 12-06-2012 03:03:29 -0700, Majid Azimi wrote:
Hi guys,
Is it possible to see what queries are running on the database?
Is it a low hanging fruit to log client to server requests with syslog?
no?
then just use the querylog, that's faster and less intrusive
But you said that it wasn't possible to see what queries are currently running on the database.
yes
I guess the query log could mark that the processing started and finished. Isn't this already a full implementation of seeing what queries are running on the database (queries without endtime and started since monetdb started). And the time actually spent on individual queries historically?
I think they are only inserted after execution finished
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users