[COMMITTERS] pgsql: Change WAL-logging scheme for multixacts to be more like regular
Log Message: --- Change WAL-logging scheme for multixacts to be more like regular transaction IDs, rather than like subtrans; in particular, the information now survives a database restart. Per previous discussion, this is essential for PITR log shipping and for 2PC. Modified Files: -- pgsql/doc/src/sgml/ref: pg_resetxlog.sgml (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_resetxlog.sgml.diff?r1=1.10&r2=1.11) pgsql/src/backend/access/heap: heapam.c (r1.193 -> r1.194) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/heapam.c.diff?r1=1.193&r2=1.194) pgsql/src/backend/access/transam: multixact.c (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/multixact.c.diff?r1=1.4&r2=1.5) rmgr.c (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/rmgr.c.diff?r1=1.18&r2=1.19) xlog.c (r1.197 -> r1.198) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.197&r2=1.198) pgsql/src/bin/pg_controldata: pg_controldata.c (r1.24 -> r1.25) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_controldata/pg_controldata.c.diff?r1=1.24&r2=1.25) pgsql/src/bin/pg_resetxlog: pg_resetxlog.c (r1.33 -> r1.34) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_resetxlog/pg_resetxlog.c.diff?r1=1.33&r2=1.34) pgsql/src/include/access: htup.h (r1.74 -> r1.75) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/htup.h.diff?r1=1.74&r2=1.75) multixact.h (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/multixact.h.diff?r1=1.2&r2=1.3) xlog.h (r1.64 -> r1.65) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/xlog.h.diff?r1=1.64&r2=1.65) pgsql/src/include: c.h (r1.184 -> r1.185) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/c.h.diff?r1=1.184&r2=1.185) pgsql/src/include/catalog: pg_control.h (r1.22 -> r1.23) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_control.h.diff?r1=1.22&r2=1.23) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Remove grammar productions for prefix and postfix % and ^
Log Message: --- Remove grammar productions for prefix and postfix % and ^ operators, as well as the existing pg_catalog entries for prefix and postfix %. These have never been documented, though they did appear in one old regression test. This avoids surprising behavior in cases like "SELECT -25 % -10". Per recent discussion. Note: although there is a catalog change here, I did not force initdb since there's no harm in leaving the inaccessible entries in one's copy of pg_operator. Modified Files: -- pgsql/doc/src/sgml/ref: comment.sgml (r1.28 -> r1.29) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/comment.sgml.diff?r1=1.28&r2=1.29) pgsql/src/backend/parser: gram.y (r2.491 -> r2.492) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.491&r2=2.492) pgsql/src/include/catalog: pg_operator.h (r1.132 -> r1.133) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_operator.h.diff?r1=1.132&r2=1.133) pgsql/src/test/regress/expected: float8-exp-three-digits-win32.out (r1.6 -> r1.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/float8-exp-three-digits-win32.out.diff?r1=1.6&r2=1.7) float8-exp-three-digits.out (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/float8-exp-three-digits.out.diff?r1=1.11&r2=1.12) float8-small-is-zero.out (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/float8-small-is-zero.out.diff?r1=1.9&r2=1.10) float8-small-is-zero_1.out (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/float8-small-is-zero_1.out.diff?r1=1.3&r2=1.4) float8.out (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/float8.out.diff?r1=1.23&r2=1.24) pgsql/src/test/regress/sql: float8.sql (r1.14 -> r1.15) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/float8.sql.diff?r1=1.14&r2=1.15) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Marginal hack to avoid spending a lot of time in find_join_rel
Log Message: --- Marginal hack to avoid spending a lot of time in find_join_rel during large planning problems: when the list of join rels gets too long, make an auxiliary hash table that hashes on the identifying Bitmapset. Modified Files: -- pgsql/src/backend/nodes: bitmapset.c (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/bitmapset.c.diff?r1=1.7&r2=1.8) pgsql/src/backend/optimizer/geqo: geqo_eval.c (r1.74 -> r1.75) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/geqo/geqo_eval.c.diff?r1=1.74&r2=1.75) geqo_main.c (r1.49 -> r1.50) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/geqo/geqo_main.c.diff?r1=1.49&r2=1.50) pgsql/src/backend/optimizer/plan: planmain.c (r1.83 -> r1.84) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planmain.c.diff?r1=1.83&r2=1.84) pgsql/src/backend/optimizer/util: relnode.c (r1.68 -> r1.69) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/relnode.c.diff?r1=1.68&r2=1.69) pgsql/src/backend/utils/hash: hashfn.c (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/hash/hashfn.c.diff?r1=1.23&r2=1.24) pgsql/src/include/nodes: bitmapset.h (r1.6 -> r1.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/bitmapset.h.diff?r1=1.6&r2=1.7) relation.h (r1.111 -> r1.112) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/relation.h.diff?r1=1.111&r2=1.112) pgsql/src/include/utils: hsearch.h (r1.36 -> r1.37) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/hsearch.h.diff?r1=1.36&r2=1.37) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Remove idea of schema tablespaces: < o Allow databases and
Log Message: --- Remove idea of schema tablespaces: < o Allow databases and schemas to be moved to different tablespaces < < One complexity is whether moving a schema should move all existing < schema objects or just define the location for future object creation. < > o Allow databases to be moved to different tablespaces 484c480 < schema. Global system tables can never be moved. > tablespace. Global system tables can never be moved. Modified Files: -- pgsql/doc: TODO (r1.1555 -> r1.1556) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1555&r2=1.1556) pgsql/doc/src/FAQ: TODO.html (r1.62 -> r1.63) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.62&r2=1.63) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Simplify the planner's join clause management by storing join
Log Message: --- Simplify the planner's join clause management by storing join clauses of a relation in a flat 'joininfo' list. The former arrangement grouped the join clauses according to the set of unjoined relids used in each; however, profiling on test cases involving lots of joins proves that that data structure is a net loss. It takes more time to group the join clauses together than is saved by avoiding duplicate tests later. It doesn't help any that there are usually not more than one or two clauses per group ... Modified Files: -- pgsql/src/backend/nodes: copyfuncs.c (r1.305 -> r1.306) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c.diff?r1=1.305&r2=1.306) equalfuncs.c (r1.242 -> r1.243) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c.diff?r1=1.242&r2=1.243) outfuncs.c (r1.254 -> r1.255) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c.diff?r1=1.254&r2=1.255) pgsql/src/backend/optimizer: README (r1.32 -> r1.33) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/README.diff?r1=1.32&r2=1.33) pgsql/src/backend/optimizer/geqo: geqo_eval.c (r1.75 -> r1.76) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/geqo/geqo_eval.c.diff?r1=1.75&r2=1.76) pgsql/src/backend/optimizer/path: allpaths.c (r1.132 -> r1.133) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/allpaths.c.diff?r1=1.132&r2=1.133) indxpath.c (r1.181 -> r1.182) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.181&r2=1.182) joinrels.c (r1.73 -> r1.74) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinrels.c.diff?r1=1.73&r2=1.74) orindxpath.c (r1.71 -> r1.72) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/orindxpath.c.diff?r1=1.71&r2=1.72) pathkeys.c (r1.67 -> r1.68) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c.diff?r1=1.67&r2=1.68) pgsql/src/backend/optimizer/plan: initsplan.c (r1.106 -> r1.107) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/initsplan.c.diff?r1=1.106&r2=1.107) pgsql/src/backend/optimizer/prep: prepunion.c (r1.122 -> r1.123) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/prep/prepunion.c.diff?r1=1.122&r2=1.123) pgsql/src/backend/optimizer/util: joininfo.c (r1.42 -> r1.43) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/joininfo.c.diff?r1=1.42&r2=1.43) relnode.c (r1.69 -> r1.70) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/relnode.c.diff?r1=1.69&r2=1.70) restrictinfo.c (r1.36 -> r1.37) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/restrictinfo.c.diff?r1=1.36&r2=1.37) pgsql/src/include/nodes: nodes.h (r1.169 -> r1.170) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/nodes.h.diff?r1=1.169&r2=1.170) relation.h (r1.112 -> r1.113) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/relation.h.diff?r1=1.112&r2=1.113) pgsql/src/include/optimizer: joininfo.h (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/joininfo.h.diff?r1=1.29&r2=1.30) restrictinfo.h (r1.30 -> r1.31) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/restrictinfo.h.diff?r1=1.30&r2=1.31) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
