Robert Haas 3a0e4d36eb Make new event trigger facility actually do something. ...

Commit 3855968f328918b6cd1401dd11d109d471a54d40 added syntax, pg_dump,
psql support, and documentation, but the triggers didn't actually fire.
With this commit, they now do.  This is still a pretty basic facility
overall because event triggers do not get a whole lot of information
about what the user is trying to do unless you write them in C; and
there's still no option to fire them anywhere except at the very
beginning of the execution sequence, but it's better than nothing,
and a good building block for future work.

Along the way, add a regression test for ALTER LARGE OBJECT, since
testing of event triggers reveals that we haven't got one.

Dimitri Fontaine and Robert Haas

2012-07-20 11:39:01 -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

Rename I/O timing statistics columns to blk_read_time and blk_write_time.

2012-04-29 18:13:33 -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

Rename I/O timing statistics columns to blk_read_time and blk_write_time.

2012-04-29 18:13:33 -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

Make new event trigger facility actually do something.

2012-07-20 11:39:01 -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