[COMMITTERS] psqlodbc - psqlodbc: without of openssl cannot have been done.
Log Message: --- without of openssl cannot have been done. Fix did this. However,The compilation doesn't succeed if OpenSSL is not made effective now. This problem is still continued Modified Files: -- psqlodbc: configure.ac (r1.58 -> r1.59) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/configure.ac.diff?r1=1.58&r2=1.59) ---(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: Fix typo in Makefile.
Log Message: --- Fix typo in Makefile. Marko Kreen Modified Files: -- pgsql/src/backend/utils/mb/conversion_procs/euc_jis_2004_and_shift_jis_2004: Makefile (r1.1 -> r1.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/conversion_procs/euc_jis_2004_and_shift_jis_2004/Makefile.diff?r1=1.1&r2=1.2) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] psqlodbc - psqlodbc: Fixed without-openssl.
Log Message: --- Fixed without-openssl. Modified Files: -- psqlodbc: configure.ac (r1.59 -> r1.60) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/configure.ac.diff?r1=1.59&r2=1.60) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Add: > > * Allow configuration of backend priorities via the
Log Message: --- Add: > > * Allow configuration of backend priorities via the operating system > > Though backend priorities make priority inversion during lock > waits possible, research shows that this is not a huge problem. > http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php Modified Files: -- pgsql/doc: TODO (r1.2132 -> r1.2133) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2132&r2=1.2133) pgsql/doc/src/FAQ: TODO.html (r1.633 -> r1.634) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.633&r2=1.634) ---(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] bizgres - bizgres: Update the README to reflect the code changes.
Log Message: --- Update the README to reflect the code changes. Modified Files: -- bizgres/postgresql/src/backend/utils/resscheduler: README (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/resscheduler/README.diff?r1=1.10&r2=1.11) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Remove item due to lack of interest: < * %Add pg_get_acldef(),
Log Message: --- Remove item due to lack of interest: < * %Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(), < pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef() < < These would be for application use, not for use by pg_dump. < Modified Files: -- pgsql/doc: TODO (r1.2133 -> r1.2134) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2133&r2=1.2134) pgsql/doc/src/FAQ: TODO.html (r1.634 -> r1.635) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.634&r2=1.635) ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
[COMMITTERS] pgsql: Cosmetic changes: rename some struct fields, and move the
Log Message: --- Cosmetic changes: rename some struct fields, and move the fetching of pgstat table entries to a separate routine. Don't pass the pgstat database entry to do_autovacuum; rather, have it fetch it by itself. Modified Files: -- pgsql/src/backend/postmaster: autovacuum.c (r1.38 -> r1.39) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/autovacuum.c.diff?r1=1.38&r2=1.39) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Install import libraries used to link to libpq, ecpg and the
Log Message: --- Install import libraries used to link to libpq, ecpg and the backend. Modified Files: -- pgsql/src/tools/msvc: Install.pm (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/Install.pm.diff?r1=1.4&r2=1.5) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Fix array coercion expressions to ensure that the correct
Log Message: --- Fix array coercion expressions to ensure that the correct volatility is seen by code inspecting the expression. The best way to do this seems to be to drop the original representation as a function invocation, and instead make a special expression node type that represents applying the element-type coercion function to each array element. In this way the element function is exposed and will be checked for volatility. Per report from Guillaume Smet. Modified Files: -- pgsql/src/backend/catalog: dependency.c (r1.64 -> r1.65) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/dependency.c.diff?r1=1.64&r2=1.65) pgsql/src/backend/executor: execQual.c (r1.215 -> r1.216) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execQual.c.diff?r1=1.215&r2=1.216) pgsql/src/backend/nodes: copyfuncs.c (r1.371 -> r1.372) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c.diff?r1=1.371&r2=1.372) equalfuncs.c (r1.302 -> r1.303) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c.diff?r1=1.302&r2=1.303) outfuncs.c (r1.304 -> r1.305) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c.diff?r1=1.304&r2=1.305) readfuncs.c (r1.204 -> r1.205) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/readfuncs.c.diff?r1=1.204&r2=1.205) pgsql/src/backend/optimizer/path: costsize.c (r1.178 -> r1.179) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/costsize.c.diff?r1=1.178&r2=1.179) pgsql/src/backend/optimizer/util: clauses.c (r1.239 -> r1.240) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.239&r2=1.240) pgsql/src/backend/parser: parse_coerce.c (r2.151 -> r2.152) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_coerce.c.diff?r1=2.151&r2=2.152) parse_expr.c (r1.214 -> r1.215) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c.diff?r1=1.214&r2=1.215) parse_func.c (r1.194 -> r1.195) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_func.c.diff?r1=1.194&r2=1.195) pgsql/src/backend/utils/adt: arrayfuncs.c (r1.137 -> r1.138) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/arrayfuncs.c.diff?r1=1.137&r2=1.138) ri_triggers.c (r1.93 -> r1.94) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ri_triggers.c.diff?r1=1.93&r2=1.94) ruleutils.c (r1.256 -> r1.257) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ruleutils.c.diff?r1=1.256&r2=1.257) selfuncs.c (r1.230 -> r1.231) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/selfuncs.c.diff?r1=1.230&r2=1.231) pgsql/src/backend/utils/fmgr: fmgr.c (r1.104 -> r1.105) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/fmgr/fmgr.c.diff?r1=1.104&r2=1.105) pgsql/src/include/catalog: catversion.h (r1.395 -> r1.396) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h.diff?r1=1.395&r2=1.396) pg_proc.h (r1.450 -> r1.451) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h.diff?r1=1.450&r2=1.451) pgsql/src/include/nodes: execnodes.h (r1.170 -> r1.171) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/execnodes.h.diff?r1=1.170&r2=1.171) nodes.h (r1.196 -> r1.197) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/nodes.h.diff?r1=1.196&r2=1.197) primnodes.h (r1.128 -> r1.129) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/primnodes.h.diff?r1=1.128&r2=1.129) pgsql/src/include/parser: parse_coerce.h (r1.69 -> r1.70) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_coerce.h.diff?r1=1.69&r2=1.70) pgsql/src/include/utils: array.h (r1.63 -> r1.64) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/array.h.diff?r1=1.63&r2=1.64) pgsql/src/pl/plpgsql/src: pl_exec.c (r1.191 -> r1.192) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_exec.c.diff?r1=1.191&r2=1.192) ---(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 uninitialized-variable bug.
Log Message: --- Fix uninitialized-variable bug. Modified Files: -- pgsql/contrib/tsearch2: dict_syn.c (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/dict_syn.c.diff?r1=1.13&r2=1.14) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Add URL for: * Automatically create rules on views so they are
Log Message: --- Add URL for: * Automatically create rules on views so they are updateable, per SQL99 > http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php Modified Files: -- pgsql/doc: TODO (r1.2134 -> r1.2135) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2134&r2=1.2135) pgsql/doc/src/FAQ: TODO.html (r1.635 -> r1.636) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.635&r2=1.636) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Remove assertion that constraint_exclusion risks wrong answers if
Log Message: --- Remove assertion that constraint_exclusion risks wrong answers if table constraints are changed; this is no longer true now that we have a plan invalidation mechanism. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.117 -> r1.118) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.117&r2=1.118) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
