On 26th of January, Magnus Hagander committed patch:
Adds a counter that tracks number of deadlocks that occurred in each database to pg_stat_database. Magnus Hagander, reviewed by Jaime Casanova
Tag: waiting
Waiting for 9.2 – temporary file stats per database
On 26th of January, Magnus Hagander committed patch:
Add counters for number and size of temporary files used for spill-to-disk queries for each database to the pg_stat_database view. Tomas Vondra, review by Magnus Hagander
Continue reading Waiting for 9.2 – temporary file stats per database
Waiting for 9.2 – pg_basebackup from slave
On 25th of January, Simon Riggs committed patch:
Allow pg_basebackup from standby node with safety checking. Base backup follows recommended procedure, plus goes to great lengths to ensure that partial page writes are avoided. Jun Ishizuka and Fujii Masao, with minor modifications
Waiting for 9.2 – Trigger Depth
On 25th of January, Alvaro Herrera committed patch:
Add pg_trigger_depth() function This reports the depth level of triggers currently in execution, or zero if not called from inside a trigger. No catversion bump in this patch, but you have to initdb if you want access to the new function. Author: Kevin Grittner
Waiting for 9.2 – ALTER IF EXISTS
On 23th of January, Simon Riggs committed patch:
ALTER <thing> [IF EXISTS] ... allows silent DDL if required, e.g. ALTER FOREIGN TABLE IF EXISTS foo RENAME TO bar Pavel Stehule
Waiting for 9.2 – split of current_query in pg_stat_activity
On 19t of January, Magnus Hagander committed patch:
Separate state from query string in pg_stat_activity
This separates the state (running/idle/idleintransaction etc) into
it's own field ("state"), and leaves the query field containing just
query text.
The query text will now mean "current query" when a query is running
and "last query" in other states. Accordingly,the field has been
renamed from current_query to query.
Since backwards compatibility was broken anyway to make that, the procpid
field has also been renamed to pid - along with the same field in
pg_stat_replication for consistency.
Scott Mead and Magnus Hagander, review work from Greg SmithContinue reading Waiting for 9.2 – split of current_query in pg_stat_activity
Waiting for 9.2 – NULLS from pg_*_size() functions
On 19t of January, Heikki Linnakangas committed patch:
Make pg_relation_size() and friends return NULL if the object doesn't exist. That avoids errors when the functions are used in queries like "SELECT pg_relation_size(oid) FROM pg_class", and a table is dropped concurrently. Phil Sorber
Continue reading Waiting for 9.2 – NULLS from pg_*_size() functions
Waiting for 9.2 – excluding data of table from dump
On 14h of December, Andrew Dunstan committed patch:
Add --exclude-table-data option to pg_dump. Andrew Dunstan, reviewed by Josh Berkus, Robert Haas and Peter Geoghegan. This allows dumping of a table definition but not its data, on a per table basis. Table name patterns are supported just as for --exclude-table.
Continue reading Waiting for 9.2 – excluding data of table from dump
Waiting for 9.2 – Range data types
On 3rd of November, Heikki Linnakangas committed patch:
Support range data types. Selectivity estimation functions are missing for some range type operators, which is a TODO. Jeff Davis
Waiting for 9.2 – Index only scans
On 8th of October, Tom Lane committed patch:
Support index-only scans using the visibility map to avoid heap fetches. When a btree index contains all columns required by the query, and the visibility map shows that all tuples on a target heap page are visible-to-all, we don't need to fetch that heap page. This patch depends on the previous patches that made the visibility map reliable. There's a fair amount left to do here, notably trying to figure out a less chintzy way of estimating the cost of an index-only scan, but the core functionality seems ready to commit. Robert Haas and Ibrar Ahmed, with some previous work by Heikki Linnakangas.