Adding new output parameter of pg_stat_statements to identify operation of the query.

From: <husttripper(at)vip(dot)sina(dot)com>
To: "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Adding new output parameter of pg_stat_statements to identify operation of the query.
Date: 2017-02-19 09:35:42
Message-ID: 20170219093542.BF8F4440421@webmail.sinamail.sina.com.cn
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi PG hackers: When using pg_stat_statements to collect running SQL of PG, we find it is hard for our program to get exact operation type of the SQL, such as SELECT, DELETE, UPDATE, INSERT, and so on. So we modify the the source code of pg_stat_statements and add another output parameter to tell us the operation type.Of course some application know their operation type, but for us and many public databases, doing this is hard. The only way is to reparse the SQL, obviously it is too expensive for a monitoring or diagnosis system.We have done the job and are willing to post a patch. I sent one through my work mail, but it seems that my mail didn't reach the maillist, so I try again by using my personal mail account.
jasonysli

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-02-19 09:43:30 Re: Reporting xmin from VACUUMs
Previous Message Robert Haas 2017-02-19 09:29:23 Re: Parallel Append implementation