[COMMITTERS] pgsql: Fix Assert failure when a fastpath function call is attempted
Log Message: --- Fix Assert failure when a fastpath function call is attempted inside an already-aborted transaction block. GetSnapshotData throws an Assert if not in a valid transaction; hence we mustn't attempt to set a snapshot for the function until after checking for aborted transaction. This is harmless AFAICT if Asserts aren't enabled (GetSnapshotData will compute a bogus snapshot, but it doesn't matter since HandleFunctionRequest will throw an error shortly anywy). Hence, not a major bug. Along the way, add some ability to log fastpath calls when statement logging is turned on. This could probably stand to be improved further, but not logging anything is clearly undesirable. Backpatched as far as 8.0; bug doesn't exist before that. Modified Files: -- pgsql/src/backend/tcop: fastpath.c (r1.86 -> r1.87) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/fastpath.c.diff?r1=1.86&r2=1.87) postgres.c (r1.486 -> r1.487) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.486&r2=1.487) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix Assert failure when a fastpath function call is attempted
Log Message: --- Fix Assert failure when a fastpath function call is attempted inside an already-aborted transaction block. GetSnapshotData throws an Assert if not in a valid transaction; hence we mustn't attempt to set a snapshot for the function until after checking for aborted transaction. This is harmless AFAICT if Asserts aren't enabled (GetSnapshotData will compute a bogus snapshot, but it doesn't matter since HandleFunctionRequest will throw an error shortly anywy). Hence, not a major bug. Along the way, add some ability to log fastpath calls when statement logging is turned on. This could probably stand to be improved further, but not logging anything is clearly undesirable. Backpatched as far as 8.0; bug doesn't exist before that. Tags: REL8_1_STABLE Modified Files: -- pgsql/src/backend/tcop: fastpath.c (r1.83.2.1 -> r1.83.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/fastpath.c.diff?r1=1.83.2.1&r2=1.83.2.2) postgres.c (r1.468.2.4 -> r1.468.2.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.468.2.4&r2=1.468.2.5) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Fix Assert failure when a fastpath function call is attempted
Log Message: --- Fix Assert failure when a fastpath function call is attempted inside an already-aborted transaction block. GetSnapshotData throws an Assert if not in a valid transaction; hence we mustn't attempt to set a snapshot for the function until after checking for aborted transaction. This is harmless AFAICT if Asserts aren't enabled (GetSnapshotData will compute a bogus snapshot, but it doesn't matter since HandleFunctionRequest will throw an error shortly anywy). Hence, not a major bug. Along the way, add some ability to log fastpath calls when statement logging is turned on. This could probably stand to be improved further, but not logging anything is clearly undesirable. Backpatched as far as 8.0; bug doesn't exist before that. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/tcop: fastpath.c (r1.77 -> r1.77.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/fastpath.c.diff?r1=1.77&r2=1.77.4.1) postgres.c (r1.440.4.5 -> r1.440.4.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.440.4.5&r2=1.440.4.6) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgbuildfarm - client-code: make template config force_every 336 ( = 2
Log Message: --- make template config force_every 336 ( = 2 weeks) instead of undef. Modified Files: -- client-code: build-farm.conf (r1.18 -> r1.19) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/build-farm.conf.diff?r1=1.18&r2=1.19) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgfouine - pgfouine: fixed a problem with NOTICE/STATEMENT couple on DDL
Log Message: --- fixed a problem with NOTICE/STATEMENT couple on DDL Modified Files: -- pgfouine/include/postgresql/lines: PostgreSQLStatementLine.class.php (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/lines/PostgreSQLStatementLine.class.php.diff?r1=1.6&r2=1.7) pgfouine/include/postgresql/parsers: PostgreSQLParser.class.php (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/parsers/PostgreSQLParser.class.php.diff?r1=1.16&r2=1.17) pgfouine/include: LogObject.class.php (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/LogObject.class.php.diff?r1=1.6&r2=1.7) pgfouine/include/postgresql: PostgreSQLRegexps.lib.php (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/PostgreSQLRegexps.lib.php.diff?r1=1.6&r2=1.7) postgresql.lib.php (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/postgresql.lib.php.diff?r1=1.5&r2=1.6) pgfouine: ChangeLog (r1.37 -> r1.38) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/ChangeLog.diff?r1=1.37&r2=1.38) Added Files: --- pgfouine/include/postgresql/lines: PostgreSQLNoticeLine.class.php (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/lines/PostgreSQLNoticeLine.class.php?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgfouine - pgfouine: improved the -report option analysis
Log Message: --- improved the -report option analysis Modified Files: -- pgfouine: pgfouine.php (r1.43 -> r1.44) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/pgfouine.php.diff?r1=1.43&r2=1.44) ChangeLog (r1.38 -> r1.39) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/ChangeLog.diff?r1=1.38&r2=1.39) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] fulldisjunction - fd: Moved the (tableID:rowID) pairs to the first
Log Message: --- Moved the (tableID:rowID) pairs to the first attribute of the tuple set for faster access. Modified Files: -- fd: algstructs.c (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algstructs.c.diff?r1=1.7&r2=1.8) algstructs.h (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algstructs.h.diff?r1=1.5&r2=1.6) algutils.c (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algutils.c.diff?r1=1.5&r2=1.6) algutils.h (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algutils.h.diff?r1=1.5&r2=1.6) odmbfd.c (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/odmbfd.c.diff?r1=1.8&r2=1.9) queues.c (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/queues.c.diff?r1=1.7&r2=1.8) tset.c (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/tset.c.diff?r1=1.3&r2=1.4) tset.h (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/tset.h.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgfouine - pgfouine: NOTICEs for a query are now displayed improved
Log Message: --- NOTICEs for a query are now displayed improved normalized queries formatting Modified Files: -- pgfouine/include/reporting: ReportAggregator.class.php (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/ReportAggregator.class.php.diff?r1=1.14&r2=1.15) HtmlReportAggregator.class.php (r1.20 -> r1.21) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/HtmlReportAggregator.class.php.diff?r1=1.20&r2=1.21) pgfouine/include: NormalizedQuery.class.php (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/NormalizedQuery.class.php.diff?r1=1.11&r2=1.12) LogObject.class.php (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/LogObject.class.php.diff?r1=1.7&r2=1.8) SlowestQueryList.class.php (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/SlowestQueryList.class.php.diff?r1=1.6&r2=1.7) pgfouine/include/reporting/reports: NormalizedReport.class.php (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/reports/NormalizedReport.class.php.diff?r1=1.8&r2=1.9) SlowestQueriesReport.class.php (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/reports/SlowestQueriesReport.class.php.diff?r1=1.8&r2=1.9) Report.class.php (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/reports/Report.class.php.diff?r1=1.9&r2=1.10) pgfouine: ChangeLog (r1.39 -> r1.40) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/ChangeLog.diff?r1=1.39&r2=1.40) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Code review for psql multiline history patch(es).
Log Message: --- Code review for psql multiline history patch(es). Fix memory leak, failure to enter commands in history if canceled by control-C, other infelicities. Modified Files: -- pgsql/src/bin/psql: command.c (r1.169 -> r1.170) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.169&r2=1.170) help.c (r1.110 -> r1.111) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/help.c.diff?r1=1.110&r2=1.111) input.c (r1.53 -> r1.54) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/input.c.diff?r1=1.53&r2=1.54) input.h (r1.27 -> r1.28) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/input.h.diff?r1=1.27&r2=1.28) mainloop.c (r1.78 -> r1.79) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/mainloop.c.diff?r1=1.78&r2=1.79) prompt.c (r1.44 -> r1.45) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/prompt.c.diff?r1=1.44&r2=1.45) tab-complete.c (r1.152 -> r1.153) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.152&r2=1.153) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Minor code cleanup: make the WIN32 case less gratuitously
Log Message: --- Minor code cleanup: make the WIN32 case less gratuitously different from the other platform-specific cases in ps_status. Modified Files: -- pgsql/src/backend/utils/misc: ps_status.c (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/ps_status.c.diff?r1=1.29&r2=1.30) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] npgsql - Npgsql: 2006-06-11 Josh Cooley <[EMAIL PROTECTED]>
Log Message: --- 2006-06-11 Josh Cooley <[EMAIL PROTECTED]> * Fixed NpgsqlCommandBuilder.cs to always qualify table names with the schema name so that the command builder can be used with tables in other schemas. Modified Files: -- Npgsql/src/Npgsql: NpgsqlCommandBuilder.cs (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql/src/Npgsql/NpgsqlCommandBuilder.cs.diff?r1=1.11&r2=1.12) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] npgsql - Npgsql2: 2006-06-11 Josh Cooley <[EMAIL PROTECTED]>
Log Message: --- 2006-06-11 Josh Cooley <[EMAIL PROTECTED]> * Fixed NpgsqlCommandBuilder.cs to always qualify table names with the schema name so that the command builder can be used with tables in other schemas. Modified Files: -- Npgsql2/src/Npgsql: NpgsqlCommandBuilder.cs (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlCommandBuilder.cs.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
