[COMMITTERS] plpsm - plpgpsm: allows stacked diagnostics entry for exceptions get
Log Message: --- allows stacked diagnostics entry for exceptions get stacked diagnostics statement support Modified Files: -- plpgpsm/src: gram.y (r1.41 -> r1.42) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/gram.y.diff?r1=1.41&r2=1.42) pl_exec.c (r1.42 -> r1.43) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/pl_exec.c.diff?r1=1.42&r2=1.43) pl_funcs.c (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/pl_funcs.c.diff?r1=1.8&r2=1.9) plpgpsm.h (r1.32 -> r1.33) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/plpgpsm.h.diff?r1=1.32&r2=1.33) plpgpsm/src/expected: plpgpsm.out (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/expected/plpgpsm.out.diff?r1=1.14&r2=1.15) plpgpsm/src/sql: plpgpsm.sql (r1.13 -> r1.14) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/sql/plpgpsm.sql.diff?r1=1.13&r2=1.14) ---(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] plpsm - plpgpsm: allow older syntax for enhanced diagnostic statement
Log Message: --- allow older syntax for enhanced diagnostic statement Modified Files: -- plpgpsm/src: gram.y (r1.42 -> r1.43) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/gram.y.diff?r1=1.42&r2=1.43) plpgpsm.h (r1.33 -> r1.34) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/plpgpsm.h.diff?r1=1.33&r2=1.34) scan.l (r1.13 -> r1.14) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/scan.l.diff?r1=1.13&r2=1.14) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] plpsm - plpgpsm: resignal statement support
Log Message: --- resignal statement support Modified Files: -- plpgpsm/src: gram.y (r1.43 -> r1.44) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/gram.y.diff?r1=1.43&r2=1.44) pl_exec.c (r1.43 -> r1.44) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/pl_exec.c.diff?r1=1.43&r2=1.44) plpgpsm.h (r1.34 -> r1.35) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/plpgpsm.h.diff?r1=1.34&r2=1.35) plpgpsm/src/expected: plpgpsm.out (r1.15 -> r1.16) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/expected/plpgpsm.out.diff?r1=1.15&r2=1.16) plpgpsm/src/sql: plpgpsm.sql (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/sql/plpgpsm.sql.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] plpsm - plpgpsm: move to contrib format
Log Message: --- move to contrib format Modified Files: -- plpgpsm/src: Makefile (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/Makefile.diff?r1=1.5&r2=1.6) Added Files: --- plpgpsm/src: magic.c (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/magic.c?rev=1.1&content-type=text/x-cvsweb-markup) plpgpsm.sql.in (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/plpgpsm.sql.in?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] plpsm - plpgpsm: magic.c isn't necessery
Log Message: --- magic.c isn't necessery Modified Files: -- plpgpsm/src: Makefile (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/Makefile.diff?r1=1.6&r2=1.7) Removed Files: - plpgpsm/src: magic.c (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/magic.c) ---(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] plpsm - plpgpsm: contrib cfg game
Log Message: --- contrib cfg game Modified Files: -- plpgpsm/src: Makefile (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/Makefile.diff?r1=1.7&r2=1.8) plpgpsm.sql.in (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/plpgpsm.sql.in.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] plpsm - plpgpsm: contrib package completation
Log Message: --- contrib package completation Modified Files: -- plpgpsm/src: Makefile (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/Makefile.diff?r1=1.8&r2=1.9) Added Files: --- plpgpsm/src: COPYRIGHT.plpgpsm (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/COPYRIGHT.plpgpsm?rev=1.1&content-type=text/x-cvsweb-markup) INSTALL.plpgpsm (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/INSTALL.plpgpsm?rev=1.1&content-type=text/x-cvsweb-markup) README.plpgpsm (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plpsm/plpgpsm/src/README.plpgpsm?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Restructure autovacuum in two processes: a dummy process, which
Log Message: --- Restructure autovacuum in two processes: a dummy process, which runs continuously, and requests vacuum runs of "autovacuum workers" to postmaster. The workers do the actual vacuum work. This allows for future improvements, like allowing multiple autovacuum jobs running in parallel. For now, the code keeps the original behavior of having a single autovac process at any time by sleeping until the previous worker has finished. Modified Files: -- pgsql/src/backend/access/transam: varsup.c (r1.77 -> r1.78) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/varsup.c.diff?r1=1.77&r2=1.78) pgsql/src/backend/bootstrap: bootstrap.c (r1.230 -> r1.231) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/bootstrap/bootstrap.c.diff?r1=1.230&r2=1.231) pgsql/src/backend/commands: vacuum.c (r1.345 -> r1.346) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.345&r2=1.346) pgsql/src/backend/postmaster: autovacuum.c (r1.31 -> r1.32) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/autovacuum.c.diff?r1=1.31&r2=1.32) pgstat.c (r1.146 -> r1.147) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/pgstat.c.diff?r1=1.146&r2=1.147) postmaster.c (r1.521 -> r1.522) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.521&r2=1.522) pgsql/src/backend/storage/ipc: ipci.c (r1.90 -> r1.91) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/ipci.c.diff?r1=1.90&r2=1.91) pgsql/src/backend/storage/lmgr: proc.c (r1.183 -> r1.184) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/proc.c.diff?r1=1.183&r2=1.184) pgsql/src/backend/tcop: postgres.c (r1.522 -> r1.523) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.522&r2=1.523) pgsql/src/backend/utils/init: miscinit.c (r1.161 -> r1.162) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/miscinit.c.diff?r1=1.161&r2=1.162) postinit.c (r1.173 -> r1.174) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/postinit.c.diff?r1=1.173&r2=1.174) pgsql/src/include: miscadmin.h (r1.191 -> r1.192) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/miscadmin.h.diff?r1=1.191&r2=1.192) pgsql/src/include/postmaster: autovacuum.h (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/postmaster/autovacuum.h.diff?r1=1.7&r2=1.8) pgsql/src/include/storage: lwlock.h (r1.33 -> r1.34) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lwlock.h.diff?r1=1.33&r2=1.34) pmsignal.h (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/pmsignal.h.diff?r1=1.16&r2=1.17) proc.h (r1.93 -> r1.94) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/proc.h.diff?r1=1.93&r2=1.94) ---(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: Restructure code that is responsible for ensuring that clauseless
Log Message: --- Restructure code that is responsible for ensuring that clauseless joins are considered when it is necessary to do so because of a join-order restriction (that is, an outer-join or IN-subselect construct). The former coding was a bit ad-hoc and inconsistent, and it missed some cases, as exposed by Mario Weilguni's recent bug report. His specific problem was that an IN could be turned into a "clauseless" join due to constant-propagation removing the IN's joinclause, and if the IN's subselect involved more than one relation and there was more than one such IN linking to the same upper relation, then the only valid join orders involve "bushy" plans but we would fail to consider the specific paths needed to get there. (See the example case added to the join regression test.) On examining the code I wonder if there weren't some other problem cases too; in particular it seems that GEQO was defending against a different set of corner cases than the main planner was. There was also an efficiency problem, in that when we did realize we needed a clauseless join because of an IN, we'd consider clauseless joins against every other relation whether this was sensible or not. It seems a better design is to use the outer-join and in-clause lists as a backup heuristic, just as the rule of joining only where there are joinclauses is a heuristic: we'll join two relations if they have a usable joinclause *or* this might be necessary to satisfy an outer-join or IN-clause join order restriction. I refactored the code to have just one place considering this instead of three, and made sure that it covered all the cases that any of them had been considering. Backpatch as far as 8.1 (which has only the IN-clause form of the disease). By rights 8.0 and 7.4 should have the bug too, but they accidentally fail to fail, because the joininfo structure used in those releases preserves some memory of there having once been a joinclause between the inner and outer sides of an IN, and so it leads the code in the right direction anyway. I'll be conservative and not touch them. Modified Files: -- pgsql/src/backend/optimizer: README (r1.37 -> r1.38) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/README.diff?r1=1.37&r2=1.38) pgsql/src/backend/optimizer/geqo: geqo_eval.c (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/geqo/geqo_eval.c.diff?r1=1.84&r2=1.85) pgsql/src/backend/optimizer/path: joinrels.c (r1.85 -> r1.86) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinrels.c.diff?r1=1.85&r2=1.86) pgsql/src/backend/optimizer/util: joininfo.c (r1.47 -> r1.48) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/joininfo.c.diff?r1=1.47&r2=1.48) pgsql/src/include/optimizer: paths.h (r1.95 -> r1.96) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.95&r2=1.96) pgsql/src/test/regress/expected: join.out (r1.28 -> r1.29) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/join.out.diff?r1=1.28&r2=1.29) join_1.out (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/join_1.out.diff?r1=1.10&r2=1.11) pgsql/src/test/regress/sql: join.sql (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/join.sql.diff?r1=1.19&r2=1.20) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Restructure code that is responsible for ensuring that clauseless
Log Message: --- Restructure code that is responsible for ensuring that clauseless joins are considered when it is necessary to do so because of a join-order restriction (that is, an outer-join or IN-subselect construct). The former coding was a bit ad-hoc and inconsistent, and it missed some cases, as exposed by Mario Weilguni's recent bug report. His specific problem was that an IN could be turned into a "clauseless" join due to constant-propagation removing the IN's joinclause, and if the IN's subselect involved more than one relation and there was more than one such IN linking to the same upper relation, then the only valid join orders involve "bushy" plans but we would fail to consider the specific paths needed to get there. (See the example case added to the join regression test.) On examining the code I wonder if there weren't some other problem cases too; in particular it seems that GEQO was defending against a different set of corner cases than the main planner was. There was also an efficiency problem, in that when we did realize we needed a clauseless join because of an IN, we'd consider clauseless joins against every other relation whether this was sensible or not. It seems a better design is to use the outer-join and in-clause lists as a backup heuristic, just as the rule of joining only where there are joinclauses is a heuristic: we'll join two relations if they have a usable joinclause *or* this might be necessary to satisfy an outer-join or IN-clause join order restriction. I refactored the code to have just one place considering this instead of three, and made sure that it covered all the cases that any of them had been considering. Backpatch as far as 8.1 (which has only the IN-clause form of the disease). By rights 8.0 and 7.4 should have the bug too, but they accidentally fail to fail, because the joininfo structure used in those releases preserves some memory of there having once been a joinclause between the inner and outer sides of an IN, and so it leads the code in the right direction anyway. I'll be conservative and not touch them. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/backend/optimizer/geqo: geqo_eval.c (r1.81.2.2 -> r1.81.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/geqo/geqo_eval.c.diff?r1=1.81.2.2&r2=1.81.2.3) pgsql/src/backend/optimizer/path: joinrels.c (r1.81.2.2 -> r1.81.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinrels.c.diff?r1=1.81.2.2&r2=1.81.2.3) pgsql/src/backend/optimizer/util: joininfo.c (r1.44.2.1 -> r1.44.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/joininfo.c.diff?r1=1.44.2.1&r2=1.44.2.2) pgsql/src/include/optimizer: paths.h (r1.93 -> r1.93.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.93&r2=1.93.2.1) pgsql/src/test/regress/expected: join.out (r1.28 -> r1.28.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/join.out.diff?r1=1.28&r2=1.28.2.1) join_1.out (r1.10 -> r1.10.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/join_1.out.diff?r1=1.10&r2=1.10.2.1) pgsql/src/test/regress/sql: join.sql (r1.19 -> r1.19.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/join.sql.diff?r1=1.19&r2=1.19.2.1) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Restructure code that is responsible for ensuring that clauseless
Log Message: --- Restructure code that is responsible for ensuring that clauseless joins are considered when it is necessary to do so because of a join-order restriction (that is, an outer-join or IN-subselect construct). The former coding was a bit ad-hoc and inconsistent, and it missed some cases, as exposed by Mario Weilguni's recent bug report. His specific problem was that an IN could be turned into a "clauseless" join due to constant-propagation removing the IN's joinclause, and if the IN's subselect involved more than one relation and there was more than one such IN linking to the same upper relation, then the only valid join orders involve "bushy" plans but we would fail to consider the specific paths needed to get there. (See the example case added to the join regression test.) On examining the code I wonder if there weren't some other problem cases too; in particular it seems that GEQO was defending against a different set of corner cases than the main planner was. There was also an efficiency problem, in that when we did realize we needed a clauseless join because of an IN, we'd consider clauseless joins against every other relation whether this was sensible or not. It seems a better design is to use the outer-join and in-clause lists as a backup heuristic, just as the rule of joining only where there are joinclauses is a heuristic: we'll join two relations if they have a usable joinclause *or* this might be necessary to satisfy an outer-join or IN-clause join order restriction. I refactored the code to have just one place considering this instead of three, and made sure that it covered all the cases that any of them had been considering. Backpatch as far as 8.1 (which has only the IN-clause form of the disease). By rights 8.0 and 7.4 should have the bug too, but they accidentally fail to fail, because the joininfo structure used in those releases preserves some memory of there having once been a joinclause between the inner and outer sides of an IN, and so it leads the code in the right direction anyway. I'll be conservative and not touch them. Tags: REL8_1_STABLE Modified Files: -- pgsql/src/backend/optimizer/geqo: geqo_eval.c (r1.77.2.1 -> r1.77.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/geqo/geqo_eval.c.diff?r1=1.77.2.1&r2=1.77.2.2) pgsql/src/backend/optimizer/path: joinrels.c (r1.76.2.1 -> r1.76.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinrels.c.diff?r1=1.76.2.1&r2=1.76.2.2) pgsql/src/include/optimizer: paths.h (r1.88.2.1 -> r1.88.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.88.2.1&r2=1.88.2.2) pgsql/src/test/regress/expected: join.out (r1.25.2.1 -> r1.25.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/join.out.diff?r1=1.25.2.1&r2=1.25.2.2) join_1.out (r1.6.2.2 -> r1.6.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/join_1.out.diff?r1=1.6.2.2&r2=1.6.2.3) pgsql/src/test/regress/sql: join.sql (r1.17.2.1 -> r1.17.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/join.sql.diff?r1=1.17.2.1&r2=1.17.2.2) ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
[COMMITTERS] pgsql: Remove useless database name from bootstrap argument processing
Log Message: --- Remove useless database name from bootstrap argument processing (including startup and bgwriter processes), and the -y flag. It's not used anywhere. Modified Files: -- pgsql/doc/src/sgml/ref: postgres-ref.sgml (r1.49 -> r1.50) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/postgres-ref.sgml.diff?r1=1.49&r2=1.50) pgsql/src/backend/bootstrap: bootstrap.c (r1.231 -> r1.232) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/bootstrap/bootstrap.c.diff?r1=1.231&r2=1.232) pgsql/src/backend/postmaster: postmaster.c (r1.522 -> r1.523) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.522&r2=1.523) pgsql/src/bin/initdb: initdb.c (r1.132 -> r1.133) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/initdb.c.diff?r1=1.132&r2=1.133) ---(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: SSL improvements: o read global SSL configuration file o add
Log Message: --- SSL improvements: o read global SSL configuration file o add GUC "ssl_ciphers" to control allowed ciphers o add libpq environment variable PGSSLKEY to control SSL hardware keys Victor B. Wagner Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.110 -> r1.111) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.110&r2=1.111) libpq.sgml (r1.228 -> r1.229) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.228&r2=1.229) runtime.sgml (r1.376 -> r1.377) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml.diff?r1=1.376&r2=1.377) pgsql/src/backend/libpq: be-secure.c (r1.77 -> r1.78) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c.diff?r1=1.77&r2=1.78) pgsql/src/backend/postmaster: postmaster.c (r1.523 -> r1.524) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.523&r2=1.524) pgsql/src/backend/utils/misc: guc.c (r1.374 -> r1.375) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.374&r2=1.375) postgresql.conf.sample (r1.207 -> r1.208) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample.diff?r1=1.207&r2=1.208) pgsql/src/include/postmaster: postmaster.h (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/postmaster/postmaster.h.diff?r1=1.15&r2=1.16) pgsql/src/interfaces/libpq: fe-secure.c (r1.92 -> r1.93) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-secure.c.diff?r1=1.92&r2=1.93) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Add two new format fields for use with to_char(), to_date() and
Log Message:
---
Add two new format fields for use with to_char(), to_date() and
to_timestamp():
- ID for day-of-week
- IDDD for day-of-year
This makes it possible to convert ISO week dates to and from text
fully represented in either week ('IYYY-IW-ID') or day-of-year
('IYYY-IDDD') format.
I have also added an 'isoyear' field for use with extract / date_part.
Brendan Jurd
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.358 -> r1.359)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.358&r2=1.359)
pgsql/src/backend/utils/adt:
date.c (r1.127 -> r1.128)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/date.c.diff?r1=1.127&r2=1.128)
datetime.c (r1.175 -> r1.176)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/datetime.c.diff?r1=1.175&r2=1.176)
formatting.c (r1.124 -> r1.125)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c.diff?r1=1.124&r2=1.125)
timestamp.c (r1.171 -> r1.172)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/timestamp.c.diff?r1=1.171&r2=1.172)
pgsql/src/include/utils:
datetime.h (r1.63 -> r1.64)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/datetime.h.diff?r1=1.63&r2=1.64)
timestamp.h (r1.66 -> r1.67)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/timestamp.h.diff?r1=1.66&r2=1.67)
pgsql/src/interfaces/ecpg/pgtypeslib:
dt.h (r1.34 -> r1.35)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/pgtypeslib/dt.h.diff?r1=1.34&r2=1.35)
pgsql/src/test/regress/expected:
timestamp.out (r1.32 -> r1.33)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/timestamp.out.diff?r1=1.32&r2=1.33)
timestamptz.out (r1.22 -> r1.23)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/timestamptz.out.diff?r1=1.22&r2=1.23)
pgsql/src/test/regress/sql:
timestamp.sql (r1.17 -> r1.18)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/timestamp.sql.diff?r1=1.17&r2=1.18)
timestamptz.sql (r1.10 -> r1.11)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/timestamptz.sql.diff?r1=1.10&r2=1.11)
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Fix another problem in 8.2 changes that allowed "one-time" qual
Log Message: --- Fix another problem in 8.2 changes that allowed "one-time" qual conditions to be checked at plan levels below the top; namely, we have to allow for Result nodes inserted just above a nestloop inner indexscan. Should think about using the general Param mechanism to pass down outer-relation variables, but for the moment we need a back-patchable solution. Per report from Phil Frost. Modified Files: -- pgsql/src/backend/executor: nodeResult.c (r1.38 -> r1.39) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeResult.c.diff?r1=1.38&r2=1.39) pgsql/src/backend/optimizer/plan: setrefs.c (r1.128 -> r1.129) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/setrefs.c.diff?r1=1.128&r2=1.129) ---(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 another problem in 8.2 changes that allowed "one-time" qual
Log Message: --- Fix another problem in 8.2 changes that allowed "one-time" qual conditions to be checked at plan levels below the top; namely, we have to allow for Result nodes inserted just above a nestloop inner indexscan. Should think about using the general Param mechanism to pass down outer-relation variables, but for the moment we need a back-patchable solution. Per report from Phil Frost. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/backend/executor: nodeResult.c (r1.34.2.3 -> r1.34.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeResult.c.diff?r1=1.34.2.3&r2=1.34.2.4) pgsql/src/backend/optimizer/plan: setrefs.c (r1.126 -> r1.126.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/setrefs.c.diff?r1=1.126&r2=1.126.2.1) ---(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: Remove tabs from SGML files to help tag alingment and improve
Log Message: --- Remove tabs from SGML files to help tag alingment and improve detection of tabs are added in the future. Modified Files: -- pgsql/doc/src/sgml: docguide.sgml (r1.70 -> r1.71) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/docguide.sgml.diff?r1=1.70&r2=1.71) ecpg.sgml (r1.80 -> r1.81) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ecpg.sgml.diff?r1=1.80&r2=1.81) func.sgml (r1.359 -> r1.360) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.359&r2=1.360) geqo.sgml (r1.38 -> r1.39) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/geqo.sgml.diff?r1=1.38&r2=1.39) gin.sgml (r2.10 -> r2.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/gin.sgml.diff?r1=2.10&r2=2.11) libpq.sgml (r1.229 -> r1.230) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.229&r2=1.230) mvcc.sgml (r2.67 -> r2.68) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/mvcc.sgml.diff?r1=2.67&r2=2.68) plperl.sgml (r2.63 -> r2.64) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plperl.sgml.diff?r1=2.63&r2=2.64) sql.sgml (r1.45 -> r1.46) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/sql.sgml.diff?r1=1.45&r2=1.46) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Remove extra character erroneously added.
Log Message: --- Remove extra character erroneously added. Modified Files: -- pgsql/doc/src/sgml: ecpg.sgml (r1.81 -> r1.82) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ecpg.sgml.diff?r1=1.81&r2=1.82) ---(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: Functions for mapping table data and table schemas to XML (a.k.a.
Log Message: --- Functions for mapping table data and table schemas to XML (a.k.a. XML export) Modified Files: -- pgsql/doc/src/sgml: func.sgml (r1.360 -> r1.361) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.360&r2=1.361) pgsql/src/backend/utils/adt: xml.c (r1.28 -> r1.29) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/xml.c.diff?r1=1.28&r2=1.29) pgsql/src/include/catalog: catversion.h (r1.384 -> r1.385) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h.diff?r1=1.384&r2=1.385) pg_proc.h (r1.443 -> r1.444) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h.diff?r1=1.443&r2=1.444) pgsql/src/include/utils: xml.h (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/xml.h.diff?r1=1.15&r2=1.16) ---(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
