Don't you have been surprised by the duration of a query (seen in psql with \timing) and the duration for the same query found in pgss ? It seems that writting the first query text to file takes some time, that high execution rate on the same query could generate waits on locks as when pgss is under pressure with too much distinct queries to store compared to the max statements allowed. All those "waits" are co-located in pgss_store function. What about adding a pgss_time counter in pgss to measure the duration of pgss_store (a guc could be added to enable/disable this) ? Knowing that there are also plans to add a planing counter in PG12, I would suggest to add plan_time, exec_time, pgss_time the sum of those 3 counters being total_time. This could help in investigating write contentions in pg_stat_statements query file, helping to define that max queries should be increased, ... A prototype is available on demand. Regards PAscal -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
