Re: [PERFORM] pg_stat_statements behavior in crash recovery

2013-06-19 Thread Sameer Thakur
>Why are you posting this to the -performance list? Sorry, maybe -general was the correct place. I thought that pg_stat_statements was a performance diagnostics tool, so -performance was the correct forum Thank you Sameer

[PERFORM] pg_stat_statements behavior in crash recovery

2013-06-19 Thread Sameer Thakur
Hello, I understand that when the pg_stat_statements.save=true the statement statistics are saved at global/pg_stat_statements.stat. This file is read on next startup and then deleted. If there is a crash i understand that pg_stat_statements.stat file is not created even if pg_stat_statements.save

Re: [PERFORM] pg_stat_statements query normalization

2013-06-19 Thread Sameer Thakur
>Why don't you play around with it and see for yourself? I did that. Populated a sample table and then queried on it multiple times for each condition (=,>,<) with different constant values. Then queried pg_stat_statements view. Saw three different records corresponding to each condition query text

[PERFORM] pg_stat_statements query normalization

2013-06-16 Thread Sameer Thakur
Hello, Reading code documentation of pg_stat_statements it says * As of Postgres 9.2, this module normalizes query entries. Normalization * is a process whereby similar queries, typically differing only in their * constants (though the exact rules are somewhat more subtle than that) are * reco

[PERFORM] pg_statsinfo : error could not connect to repository

2013-05-21 Thread Sameer Thakur
Hello, After executing make install for pg_statsinfo when i start the server i see error ERROR: could not connect to repository WARNING: writer discards 1 items LOG: pg_statsinfo launcher shutting down DEBUG: shmem_exit(0): 0 callbacks to make DEBUG: proc_exit(0): 0 callbacks to make DEBUG: ex

[PERFORM] Predicate information in EXPLAIN Command

2013-05-14 Thread Sameer Thakur
Hello, I am trying to find predicate information for a given SQL query plan as provided by Oracle using DBMS_XPLAN. I am looking at the EXPLAIN command for getting this query plan information, with no luck so far. Does the EXPLAIN command provide predicate information? Thank you Sameer