Tom Lane e969f9a780 Save a few cycles while creating "sticky" entries in pg_stat_statements. ...

There's no need to sit there and increment the stats when we know all the
increments would be zero anyway.  The actual additions might not be very
expensive, but skipping acquisition of the spinlock seems like a good
thing.  Pushing the logic about initialization of the usage count down into
entry_alloc() allows us to do that while making the code actually simpler,
not more complex.  Expansion on a suggestion by Peter Geoghegan.

2012-04-09 11:16:04 -04:00

..

Makefile

Make EXPLAIN (BUFFERS) track blocks dirtied, as well as those written.

2012-02-22 20:33:05 -05:00

pg_stat_statements--1.0--1.1.sql

Expose track_iotiming information via pg_stat_statements.

2012-03-27 15:18:49 -04:00

pg_stat_statements--1.0.sql

Throw a useful error message if an extension script file is fed to psql.

2011-10-12 15:45:03 -04:00

pg_stat_statements--1.1.sql

Expose track_iotiming information via pg_stat_statements.

2012-03-27 15:18:49 -04:00

pg_stat_statements--unpackaged--1.0.sql

Throw a useful error message if an extension script file is fed to psql.

2011-10-12 15:45:03 -04:00

pg_stat_statements.c

Save a few cycles while creating "sticky" entries in pg_stat_statements.

2012-04-09 11:16:04 -04:00

pg_stat_statements.control

Make EXPLAIN (BUFFERS) track blocks dirtied, as well as those written.

2012-02-22 20:33:05 -05:00