[COMMITTERS] npgsql - Npgsql: 2006-02-06 Francisco Figueiredo Jr.
Log Message: --- 2006-02-06 Francisco Figueiredo Jr. <[EMAIL PROTECTED]> * NpgsqlCommand.cs: [#1000500] Problem with parsing parameters when using Command.Prepare(); Thanks Hubert Fongarnand for patch! Modified Files: -- Npgsql/src/Npgsql: NpgsqlCommand.cs (r1.86 -> r1.87) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql/src/Npgsql/NpgsqlCommand.cs.diff?r1=1.86&r2=1.87) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] psqlodbc - psqlodbc: Improve the dalay load import behavior in case of
Log Message: --- Improve the dalay load import behavior in case of library load failure. Tags: REL-07_03_ENHANCED Modified Files: -- psqlodbc: connection.c (r1.87.2.6 -> r1.87.2.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.c.diff?r1=1.87.2.6&r2=1.87.2.7) dlg_specific.h (r1.38.2.3 -> r1.38.2.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/dlg_specific.h.diff?r1=1.38.2.3&r2=1.38.2.4) dlg_wingui.c (r1.9.4.4 -> r1.9.4.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/dlg_wingui.c.diff?r1=1.9.4.4&r2=1.9.4.5) loadlib.c (r1.1.2.3 -> r1.1.2.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/loadlib.c.diff?r1=1.1.2.3&r2=1.1.2.4) loadlib.h (r1.1.2.3 -> r1.1.2.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/loadlib.h.diff?r1=1.1.2.3&r2=1.1.2.4) psqlodbc.c (r1.26.4.3 -> r1.26.4.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/psqlodbc.c.diff?r1=1.26.4.3&r2=1.26.4.4) psqlodbc.h (r1.82.2.6 -> r1.82.2.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/psqlodbc.h.diff?r1=1.82.2.6&r2=1.82.2.7) socket.c (r1.37.2.7 -> r1.37.2.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/socket.c.diff?r1=1.37.2.7&r2=1.37.2.8) win32_30w.mak (r1.7.2.7 -> r1.7.2.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/win32_30w.mak.diff?r1=1.7.2.7&r2=1.7.2.8) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Check number of affixes to prevent core dump with zero number of
Log Message: --- Check number of affixes to prevent core dump with zero number of affixes Modified Files: -- pgsql/contrib/tsearch2/ispell: spell.c (r1.25 -> r1.26) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/ispell/spell.c.diff?r1=1.25&r2=1.26) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Improve the tests to see if ScalarArrayOpExpr is strict.
Log Message: --- Improve the tests to see if ScalarArrayOpExpr is strict. Original coding would basically punt in all cases for 'foo <> ALL (array)', which resulted in a performance regression for NOT IN compared to what we were doing in 8.1 and before. Per report from Pavel Stehule. Modified Files: -- pgsql/src/backend/optimizer/util: clauses.c (r1.207 -> r1.208) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.207&r2=1.208) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Fix HTML alignment in PQprint.
Log Message: --- Fix HTML alignment in PQprint. Christoph Zwerschke Modified Files: -- pgsql/src/interfaces/libpq: fe-print.c (r1.65 -> r1.66) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-print.c.diff?r1=1.65&r2=1.66) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix HTML alignment in PQprint.
Log Message: --- Fix HTML alignment in PQprint. Christoph Zwerschke Tags: REL8_1_STABLE Modified Files: -- pgsql/src/interfaces/libpq: fe-print.c (r1.64.2.1 -> r1.64.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-print.c.diff?r1=1.64.2.1&r2=1.64.2.2) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Split up wal-logging items: < * Allow control over which tables
Log Message: --- Split up wal-logging items: < * Allow control over which tables are WAL-logged [walcontrol] > * Allow WAL logging to be turned off for a table, but the table > might be dropped or truncated during crash recovery [walcontrol] < commit. To do this, only a single writer can modify the table, and < writes must happen only on new pages. Readers can continue accessing < the table. This would affect COPY, and perhaps INSERT/UPDATE too. < Another option is to avoid transaction logging entirely and truncate < or drop the table on crash recovery. These should be implemented < using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | < STABLE | DEFAULT ]. Tables using non-default logging should not use < referential integrity with default-logging tables, and tables using < stable logging probably can not have indexes. One complexity is < the handling of indexes on TOAST tables. > commit. This should be implemented using ALTER TABLE, e.g. ALTER > TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using > non-default logging should not use referential integrity with > default-logging tables. A table without dirty buffers during a > crash could perhaps avoid the drop/truncate. > > * Allow WAL logging to be turned off for a table, but the table would > avoid being truncated/dropped [walcontrol] > > To do this, only a single writer can modify the table, and writes > must happen only on new pages so the new pages can be removed during > crash recovery. Readers can continue accessing the table. Such > tables probably cannot have indexes. One complexity is the handling > of indexes on TOAST tables. Modified Files: -- pgsql/doc: TODO (r1.1757 -> r1.1758) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1757&r2=1.1758) pgsql/doc/src/FAQ: TODO.html (r1.262 -> r1.263) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.262&r2=1.263) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] dbsamples - dbsamples: New Directory
Update of /cvsroot/dbsamples/dbsamples/iso-3166 In directory pgfoundry.org:/tmp/cvs-serv97165/iso-3166 Log Message: Directory /cvsroot/dbsamples/dbsamples/iso-3166 added to the repository ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] dbsamples - dbsamples: New iso-3166 data
Log Message: --- New iso-3166 data Added Files: --- dbsamples/iso-3166: iso-3166.sql (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/dbsamples/dbsamples/iso-3166/iso-3166.sql?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] dbsamples - dbsamples: Add encoding and transaction and analyze
Log Message: --- Add encoding and transaction and analyze Modified Files: -- dbsamples/iso-3166: iso-3166.sql (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/dbsamples/dbsamples/iso-3166/iso-3166.sql.diff?r1=1.1&r2=1.2) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
