Thread: pgsql: Fix some issues that prevent this file to be processed by
pgsql: Fix some issues that prevent this file to be processed by
From
alvherre@postgresql.org (Alvaro Herrera)
Date:
Log Message: ----------- Fix some issues that prevent this file to be processed by scripts. While at it, mark a couple of items completed in 8.4: ! o -Prevent long-lived temporary tables from causing frozen-xid advancement starvation ! * -Improve performance of shared invalidation queue for multiple CPUs Also remove a couple of obsolete assignments. Modified Files: -------------- pgsql/doc: TODO (r1.2499 -> r1.2500) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2499&r2=1.2500) pgsql/doc/src/FAQ: TODO.html (r1.1005 -> r1.1006) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html?r1=1.1005&r2=1.1006)
alvherre@postgresql.org (Alvaro Herrera) writes: > While at it, mark a couple of items completed in 8.4: > ! o -Prevent long-lived temporary tables from causing frozen-xid > advancement starvation Hum, should we really cross that off as "done"? I know we put in a hack to clean up temp tables that were orphaned by crashed backends; but what of the case where a session creates a temp table and then just sits on it for billions of transactions? regards, tom lane
Tom Lane wrote: > alvherre@postgresql.org (Alvaro Herrera) writes: > > While at it, mark a couple of items completed in 8.4: > > ! o -Prevent long-lived temporary tables from causing frozen-xid > > advancement starvation > > Hum, should we really cross that off as "done"? I know we put in a hack > to clean up temp tables that were orphaned by crashed backends; but what > of the case where a session creates a temp table and then just sits on > it for billions of transactions? 'Done' mark removed. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +