Yes, it seems the pg_stat_sql function can fit the individual need of
collecting tags of query. However the new function can not return other values
of query at the same time, such as block number info, run time and so on.
Returning these values at the same time are very important.
So I
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
Hi 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
Hi 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
Hi 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
