[COMMITTERS] pgsql: Add more information about avoiding Linux OOM killer.
Log Message: --- Add more information about avoiding Linux OOM killer. by Toru SHIMOGAKI Modified Files: -- pgsql/doc/src/sgml: runtime.sgml (r1.378 -> r1.379) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml.diff?r1=1.378&r2=1.379) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Minor edits
Log Message: --- Minor edits Modified Files: -- pgsql/doc/src/sgml: runtime.sgml (r1.379 -> r1.380) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml.diff?r1=1.379&r2=1.380) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsnmpd - pgsnmpd: Fix return values of rdbmsDbTable_cache_load so they
Log Message: --- Fix return values of rdbmsDbTable_cache_load so they make sense Modified Files: -- pgsnmpd: rdbmsDbTable_data_access.c (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbTable_data_access.c.diff?r1=1.4&r2=1.5) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsnmpd - pgsnmpd: Add support for rdbmsDbInfoTable (which is
Log Message: --- Add support for rdbmsDbInfoTable (which is surprisingly complete) Modified Files: -- pgsnmpd: Makefile (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/Makefile.diff?r1=1.4&r2=1.5) pgsnmpd.c (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/pgsnmpd.c.diff?r1=1.4&r2=1.5) rdbmsDbTable_data_access.c (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbTable_data_access.c.diff?r1=1.5&r2=1.6) Added Files: --- pgsnmpd: rdbmsDbInfoTable.c (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable.c?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable.h?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_data_access.c (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_data_access.c?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_data_access.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_data_access.h?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_data_get.c (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_data_get.c?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_data_get.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_data_get.h?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_data_set.c (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_data_set.c?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_data_set.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_data_set.h?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_enums.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_enums.h?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_interface.c (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_interface.c?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_interface.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_interface.h?rev=1.1&content-type=text/x-cvsweb-markup) rdbmsDbInfoTable_oids.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/rdbmsDbInfoTable_oids.h?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Add script to build documentation on win32 without mingw
Log Message: --- Add script to build documentation on win32 without mingw Modified Files: -- pgsql/src/tools/msvc: Solution.pm (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/Solution.pm.diff?r1=1.13&r2=1.14) Added Files: --- pgsql/src/tools/msvc: builddoc.bat (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/builddoc.bat?rev=1.1&content-type=text/x-cvsweb-markup) ---(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: ported the code to 8.2 with the gracious help of
Log Message: --- ported the code to 8.2 with the gracious help of jeremy drake Modified Files: -- fd: algstructs.c (r1.24 -> r1.25) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algstructs.c.diff?r1=1.24&r2=1.25) algstructs.h (r1.19 -> r1.20) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algstructs.h.diff?r1=1.19&r2=1.20) algutils.c (r1.23 -> r1.24) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algutils.c.diff?r1=1.23&r2=1.24) getfdr.c (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/getfdr.c.diff?r1=1.3&r2=1.4) queues.h (r1.12 -> r1.13) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/queues.h.diff?r1=1.12&r2=1.13) tset.c (r1.17 -> r1.18) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/tset.c.diff?r1=1.17&r2=1.18) tsetfuncs.h (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/tsetfuncs.h.diff?r1=1.14&r2=1.15) ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
[COMMITTERS] pgsql: Fix oversight in original coding of inline_function(): since
Log Message: --- Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Along the way, fix an omission in eval_const_expressions_mutator: it failed to copy the relabelformat field when processing a RelabelType. No known observable failures from this, but it definitely isn't intended behavior. Modified Files: -- pgsql/src/backend/optimizer/util: clauses.c (r1.236 -> r1.237) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.236&r2=1.237) ---(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] pgsql: Fix oversight in original coding of inline_function(): since
Log Message: --- Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Along the way, fix an omission in eval_const_expressions_mutator: it failed to copy the relabelformat field when processing a RelabelType. No known observable failures from this, but it definitely isn't intended behavior. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/backend/optimizer/util: clauses.c (r1.223.2.1 -> r1.223.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.223.2.1&r2=1.223.2.2) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Fix oversight in original coding of inline_function(): since
Log Message: --- Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Along the way, fix an omission in eval_const_expressions_mutator: it failed to copy the relabelformat field when processing a RelabelType. No known observable failures from this, but it definitely isn't intended behavior. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/optimizer/util: clauses.c (r1.186.4.5 -> r1.186.4.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.186.4.5&r2=1.186.4.6) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix oversight in original coding of inline_function(): since
Log Message: --- Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Along the way, fix an omission in eval_const_expressions_mutator: it failed to copy the relabelformat field when processing a RelabelType. No known observable failures from this, but it definitely isn't intended behavior. Tags: REL8_1_STABLE Modified Files: -- pgsql/src/backend/optimizer/util: clauses.c (r1.201.2.2 -> r1.201.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.201.2.2&r2=1.201.2.3) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix oversight in original coding of inline_function(): since
Log Message: --- Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Along the way, fix an omission in eval_const_expressions_mutator: it failed to copy the relabelformat field when processing a RelabelType. No known observable failures from this, but it definitely isn't intended behavior. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/optimizer/util: clauses.c (r1.154.2.5 -> r1.154.2.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.154.2.5&r2=1.154.2.6) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
