[HACKERS] Adding new output parameter of pg_stat_statements to identify operation of the query. - Mailing list pgsql-hackers

From
Subject [HACKERS] Adding new output parameter of pg_stat_statements to identify operation of the query.
Date
Msg-id 20170219093542.BF8F4440421@webmail.sinamail.sina.com.cn
Whole thread Raw
Responses Re: [HACKERS] Adding new output parameter of pg_stat_statements toidentify operation of the query.  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
List 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

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Parallel Append implementation
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Reporting xmin from VACUUMs