[COMMITTERS] pgsql: Turn off zero_damaged_pages in the right place (ie, in the

2006-03-07 Thread Tom Lane
Log Message: --- Turn off zero_damaged_pages in the right place (ie, in the autovac process not in the postmaster) and with the right GucSource (needs to be a nontransactional source since we've not started an xact yet). Modified Files: -- pgsql/src/backend/postmaster:

[COMMITTERS] pgsql: Repair old performance bug in tuplesort.c/logtape.c.

2006-03-07 Thread Tom Lane
Log Message: --- Repair old performance bug in tuplesort.c/logtape.c. In the case where we are doing the final merge pass on-the-fly, and not writing the data back onto a 'tape', the number of free blocks in the tape set will become large, leading to a lot of time wasted in ltsReleaseBlock

[COMMITTERS] pgfouine - pgfouine: fixed an infinite loop when duration and count are

2006-03-07 Thread User Gsmet
Log Message: --- fixed an infinite loop when duration and count are exactly identical for two different normalized queries Modified Files: -- pgfouine/include/listeners/query: NormalizedQueriesListener.class.php (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cg

[COMMITTERS] pgfouine - pgfouine: updated ChangeLog

2006-03-07 Thread User Gsmet
Log Message: --- updated ChangeLog Modified Files: -- pgfouine: ChangeLog (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/ChangeLog.diff?r1=1.16&r2=1.17) ---(end of broadcast)-

[COMMITTERS] pgsql: Further examination of ltsReleaseBlock usage shows that it's got

2006-03-07 Thread Tom Lane
Log Message: --- Further examination of ltsReleaseBlock usage shows that it's got a performance issue during regular merge passes not only the 'final merge' case. The original design contemplated that there would never be more than about one free block per 'tape', hence no need for an effi

[COMMITTERS] bizgres - bizgres: Added support for sql statement to be run on db

2006-03-07 Thread User Nwakefield
Log Message: --- Added support for sql statement to be run on db connection, such as the setting of the search_path on postgresql. Added support for pre and post sql to run on the JDBCWriter. Modified Files: -- bizgres/KETL/src/com/kni/etl/ketl/writer: JasperReport

[COMMITTERS] pgsql: Update /contrib regression tests for escape_string_warning.

2006-03-07 Thread Bruce Momjian
Log Message: --- Update /contrib regression tests for escape_string_warning. Modified Files: -- pgsql/contrib/earthdistance: earthdistance.sql.in (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/earthdistance/earthdistance.sql.in.di

[COMMITTERS] pgsql: Adjust PL regression tests for escape_string_warning.

2006-03-07 Thread Bruce Momjian
Log Message: --- Adjust PL regression tests for escape_string_warning. Modified Files: -- pgsql/src/pl/plpython/expected: plpython_function.out (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/plpython_function.out.d

[COMMITTERS] pgsql: Adjust plpython for escape_string_warning.

2006-03-07 Thread Bruce Momjian
Log Message: --- Adjust plpython for escape_string_warning. Modified Files: -- pgsql/src/pl/plpython/expected: plpython_function.out (r1.5 -> r1.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/plpython_function.out.diff?r1=1.5&