[COMMITTERS] pgsql: Update preload_library magic block wording.
Log Message: --- Update preload_library magic block wording. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.63 -> r1.64) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.63&r2=1.64) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Add LDAP documentation missed in code patch.
Log Message: --- Add LDAP documentation missed in code patch. Magnus Hagander Modified Files: -- pgsql/doc/src/sgml: client-auth.sgml (r1.89 -> r1.90) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/client-auth.sgml.diff?r1=1.89&r2=1.90) installation.sgml (r1.256 -> r1.257) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/installation.sgml.diff?r1=1.256&r2=1.257) ---(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: Add URL for ISO date/time syntax: > >
Log Message: --- Add URL for ISO date/time syntax: > > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php > Modified Files: -- pgsql/doc: TODO (r1.1882 -> r1.1883) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1882&r2=1.1883) pgsql/doc/src/FAQ: TODO.html (r1.385 -> r1.386) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.385&r2=1.386) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Add to locale TODO.detail.
Log Message: --- Add to locale TODO.detail. Modified Files: -- pgsql/doc/TODO.detail: locale (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/locale.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Add URL for: > * Allow protocol-level BIND parameter values to
Log Message: --- Add URL for: > * Allow protocol-level BIND parameter values to be logged > > http://archives.postgresql.org/pgsql-hackers/2006-02/msg00165.php Modified Files: -- pgsql/doc: TODO (r1.1883 -> r1.1884) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1883&r2=1.1884) pgsql/doc/src/FAQ: TODO.html (r1.386 -> r1.387) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.386&r2=1.387) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Add: > o Fix problems with RETURN NEXT on tables with >
Log Message: --- Add: > o Fix problems with RETURN NEXT on tables with > dropped/added columns after function creation > > > http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php Modified Files: -- pgsql/doc: TODO (r1.1884 -> r1.1885) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1884&r2=1.1885) pgsql/doc/src/FAQ: TODO.html (r1.387 -> r1.388) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.387&r2=1.388) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: > o Add PL/Python tracebacks > >
Log Message: --- > o Add PL/Python tracebacks > > > http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php Modified Files: -- pgsql/doc: TODO (r1.1885 -> r1.1886) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1885&r2=1.1886) pgsql/doc/src/FAQ: TODO.html (r1.388 -> r1.389) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.388&r2=1.389) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: > > * Add support for public SYNONYMS > >
Log Message: --- > > * Add support for public SYNONYMS > > http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php Modified Files: -- pgsql/doc: TODO (r1.1886 -> r1.1887) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1886&r2=1.1887) pgsql/doc/src/FAQ: TODO.html (r1.389 -> r1.390) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.389&r2=1.390) ---(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: Add URL for freespace map filling.
Log Message: --- Add URL for freespace map filling. > > http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php > Modified Files: -- pgsql/doc: TODO (r1.1887 -> r1.1888) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1887&r2=1.1888) pgsql/doc/src/FAQ: TODO.html (r1.390 -> r1.391) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.390&r2=1.391) ---(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: Add URL to: * Auto-fill the free space map by scanning the
Log Message: --- Add URL to: * Auto-fill the free space map by scanning the buffer cache or by checking pages written by the background writer Modified Files: -- pgsql/doc: TODO (r1.1888 -> r1.1889) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1888&r2=1.1889) pgsql/doc/src/FAQ: TODO.html (r1.391 -> r1.392) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.391&r2=1.392) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Fix problems with cached tuple descriptors disappearing while
Log Message: --- Fix problems with cached tuple descriptors disappearing while still in use by creating a reference-count mechanism, similar to what we did a long time ago for catcache entries. The back branches have an ugly solution involving lots of extra copies, but this way is more efficient. Reference counting is only applied to tupdescs that are actually in caches --- there seems no need to use it for tupdescs that are generated in the executor, since they'll go away during plan shutdown by virtue of being in the per-query memory context. Neil Conway and Tom Lane Modified Files: -- pgsql/src/backend/access/common: tupdesc.c (r1.116 -> r1.117) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/common/tupdesc.c.diff?r1=1.116&r2=1.117) pgsql/src/backend/access/heap: tuptoaster.c (r1.59 -> r1.60) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/tuptoaster.c.diff?r1=1.59&r2=1.60) pgsql/src/backend/commands: tablecmds.c (r1.184 -> r1.185) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablecmds.c.diff?r1=1.184&r2=1.185) pgsql/src/backend/executor: execJunk.c (r1.52 -> r1.53) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execJunk.c.diff?r1=1.52&r2=1.53) execMain.c (r1.270 -> r1.271) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execMain.c.diff?r1=1.270&r2=1.271) execQual.c (r1.190 -> r1.191) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execQual.c.diff?r1=1.190&r2=1.191) execTuples.c (r1.93 -> r1.94) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execTuples.c.diff?r1=1.93&r2=1.94) execUtils.c (r1.134 -> r1.135) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execUtils.c.diff?r1=1.134&r2=1.135) nodeBitmapHeapscan.c (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeBitmapHeapscan.c.diff?r1=1.11&r2=1.12) nodeFunctionscan.c (r1.38 -> r1.39) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeFunctionscan.c.diff?r1=1.38&r2=1.39) nodeHashjoin.c (r1.81 -> r1.82) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeHashjoin.c.diff?r1=1.81&r2=1.82) nodeIndexscan.c (r1.113 -> r1.114) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeIndexscan.c.diff?r1=1.113&r2=1.114) nodeMergejoin.c (r1.79 -> r1.80) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeMergejoin.c.diff?r1=1.79&r2=1.80) nodeSeqscan.c (r1.58 -> r1.59) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeSeqscan.c.diff?r1=1.58&r2=1.59) nodeSubplan.c (r1.74 -> r1.75) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeSubplan.c.diff?r1=1.74&r2=1.75) nodeSubqueryscan.c (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeSubqueryscan.c.diff?r1=1.29&r2=1.30) nodeTidscan.c (r1.48 -> r1.49) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeTidscan.c.diff?r1=1.48&r2=1.49) pgsql/src/backend/optimizer/util: clauses.c (r1.211 -> r1.212) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.211&r2=1.212) pgsql/src/backend/parser: parse_coerce.c (r2.138 -> r2.139) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_coerce.c.diff?r1=2.138&r2=2.139) parse_target.c (r1.142 -> r1.143) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_target.c.diff?r1=1.142&r2=1.143) pgsql/src/backend/utils/adt: rowtypes.c (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/rowtypes.c.diff?r1=1.15&r2=1.16) ruleutils.c (r1.223 -> r1.224) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ruleutils.c.diff?r1=1.223&r2=1.224) pgsql/src/backend/utils/cache: relcache.c (r1.241 -> r1.242) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/relcache.c.diff?r1=1.241&r2=1.242) typcache.c (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/typcache.c.diff?r1=1.18&r2=1.19) pgsql/src/backend/utils/fmgr: funcapi.c (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/fmgr/funcapi.c.diff?r1=1.29&r2=1.30) pgsql/src/backend/utils/resowner: README (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/resowner/README.dif
[COMMITTERS] pgsql: Add: > * Consider shrinking expired tuples to just their headers
Log Message: --- Add: > * Consider shrinking expired tuples to just their headers > http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php Modified Files: -- pgsql/doc: TODO (r1.1889 -> r1.1890) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1889&r2=1.1890) pgsql/doc/src/FAQ: TODO.html (r1.392 -> r1.393) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.392&r2=1.393) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Add URL for updatable views: >
Log Message: --- Add URL for updatable views: > http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php Modified Files: -- pgsql/doc: TODO (r1.1890 -> r1.1891) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1890&r2=1.1891) pgsql/doc/src/FAQ: TODO.html (r1.393 -> r1.394) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.393&r2=1.394) ---(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] pgguid - pgguid: initial version
Log Message: --- initial version Added Files: --- pgguid: crypto.h (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/crypto.h?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgguid - pgguid: initial version
Log Message: --- initial version Added Files: --- pgguid: crypto.c (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/crypto.c?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] pgguid - pgguid: deleting project files
Log Message: --- deleting project files Removed Files: - pgguid: License.txt (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/License.txt) crypto.c (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/crypto.c) crypto.h (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/crypto.h) guid.c (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/guid.c) guid.h (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/guid.h) pgguid.c (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/pgguid.c) pgguid.h (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/pgguid.h) pgguid/.settings: org.eclipse.cdt.managedbuilder.core.prefs (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgguid/pgguid/.settings/org.eclipse.cdt.managedbuilder.core.prefs) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Add URL for currency type: >
Log Message: --- Add URL for currency type: > http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php Modified Files: -- pgsql/doc: TODO (r1.1891 -> r1.1892) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1891&r2=1.1892) pgsql/doc/src/FAQ: TODO.html (r1.394 -> r1.395) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.394&r2=1.395) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: DROP ...
Log Message: --- DROP ... IF EXISTS for the following cases: language, tablespace, trigger, rule, opclass, function, aggregate. operator, and cast. Modified Files: -- pgsql/src/backend/commands: aggregatecmds.c (r1.34 -> r1.35) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/aggregatecmds.c.diff?r1=1.34&r2=1.35) functioncmds.c (r1.74 -> r1.75) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/functioncmds.c.diff?r1=1.74&r2=1.75) opclasscmds.c (r1.45 -> r1.46) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/opclasscmds.c.diff?r1=1.45&r2=1.46) operatorcmds.c (r1.30 -> r1.31) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/operatorcmds.c.diff?r1=1.30&r2=1.31) proclang.c (r1.64 -> r1.65) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/proclang.c.diff?r1=1.64&r2=1.65) tablespace.c (r1.34 -> r1.35) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablespace.c.diff?r1=1.34&r2=1.35) trigger.c (r1.202 -> r1.203) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/trigger.c.diff?r1=1.202&r2=1.203) pgsql/src/backend/nodes: copyfuncs.c (r1.335 -> r1.336) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c.diff?r1=1.335&r2=1.336) equalfuncs.c (r1.271 -> r1.272) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c.diff?r1=1.271&r2=1.272) pgsql/src/backend/parser: gram.y (r2.545 -> r2.546) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.545&r2=2.546) pgsql/src/backend/rewrite: rewriteRemove.c (r1.64 -> r1.65) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/rewrite/rewriteRemove.c.diff?r1=1.64&r2=1.65) pgsql/src/backend/tcop: utility.c (r1.257 -> r1.258) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/utility.c.diff?r1=1.257&r2=1.258) pgsql/src/include/commands: trigger.h (r1.57 -> r1.58) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/commands/trigger.h.diff?r1=1.57&r2=1.58) pgsql/src/include/nodes: parsenodes.h (r1.310 -> r1.311) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h.diff?r1=1.310&r2=1.311) pgsql/src/include/rewrite: rewriteRemove.h (r1.21 -> r1.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/rewrite/rewriteRemove.h.diff?r1=1.21&r2=1.22) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [COMMITTERS] pgsql: DROP ...
On Fri, 2006-06-16 at 17:23 -0300, Andrew Dunstan wrote: > DROP ... IF EXISTS for the following cases: > language, tablespace, trigger, rule, opclass, function, aggregate. > operator, and cast. Documentation? -Neil ---(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
Re: [COMMITTERS] pgsql: DROP ...
Neil Conway wrote: On Fri, 2006-06-16 at 17:23 -0300, Andrew Dunstan wrote: DROP ... IF EXISTS for the following cases: language, tablespace, trigger, rule, opclass, function, aggregate. operator, and cast. Documentation? -Neil It's coming. I just wanted to make sure I didn't have yet another round of bitrot. cheers andrew ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Add URL for ISO dates: >
Log Message: --- Add URL for ISO dates: > http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php Modified Files: -- pgsql/doc: TODO (r1.1892 -> r1.1893) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1892&r2=1.1893) pgsql/doc/src/FAQ: TODO.html (r1.395 -> r1.396) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.395&r2=1.396) ---(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: Document issues with non-default tablespaces and pg_dumpall
Log Message: --- Document issues with non-default tablespaces and pg_dumpall restores. Backpatch documentation addition to 8.1.X. Modified Files: -- pgsql/doc/src/sgml/ref: pg_dumpall.sgml (r1.55 -> r1.56) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_dumpall.sgml.diff?r1=1.55&r2=1.56) pgsql/src/bin/pg_dump: pg_dumpall.c (r1.79 -> r1.80) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dumpall.c.diff?r1=1.79&r2=1.80) ---(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: Document issues with non-default tablespaces and pg_dumpall
Log Message: --- Document issues with non-default tablespaces and pg_dumpall restores. Backpatch documentation addition to 8.1.X. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml/ref: pg_dumpall.sgml (r1.55 -> r1.55.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_dumpall.sgml.diff?r1=1.55&r2=1.55.2.1) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Add: > > * Fix CREATE CAST on DOMAINs > >
Log Message: --- Add: > > * Fix CREATE CAST on DOMAINs > > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php Modified Files: -- pgsql/doc: TODO (r1.1893 -> r1.1894) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1893&r2=1.1894) pgsql/doc/src/FAQ: TODO.html (r1.396 -> r1.397) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.396&r2=1.397) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Add: > o Allow PL/python to composite types and result sets >
Log Message: --- Add: > o Allow PL/python to composite types and result sets > once buggy assert-enabled versions of python can be detected > > > http://archives.postgresql.org/pgsql-patches/2006-04/msg00087.php Modified Files: -- pgsql/doc: TODO (r1.1894 -> r1.1895) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1894&r2=1.1895) pgsql/doc/src/FAQ: TODO.html (r1.397 -> r1.398) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.397&r2=1.398) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: docs for DROP ...
Log Message: --- docs for DROP ... IF EXISTS for the following cases: language, tablespace, trigger, rule, opclass, function, aggregate. operator, and cast. Modified Files: -- pgsql/doc/src/sgml/ref: drop_aggregate.sgml (r1.27 -> r1.28) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_aggregate.sgml.diff?r1=1.27&r2=1.28) drop_cast.sgml (r1.6 -> r1.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_cast.sgml.diff?r1=1.6&r2=1.7) drop_function.sgml (r1.30 -> r1.31) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_function.sgml.diff?r1=1.30&r2=1.31) drop_language.sgml (r1.21 -> r1.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_language.sgml.diff?r1=1.21&r2=1.22) drop_opclass.sgml (r1.8 -> r1.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_opclass.sgml.diff?r1=1.8&r2=1.9) drop_operator.sgml (r1.25 -> r1.26) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_operator.sgml.diff?r1=1.25&r2=1.26) drop_rule.sgml (r1.20 -> r1.21) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_rule.sgml.diff?r1=1.20&r2=1.21) drop_tablespace.sgml (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_tablespace.sgml.diff?r1=1.2&r2=1.3) drop_trigger.sgml (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_trigger.sgml.diff?r1=1.19&r2=1.20) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Clean up after someone's curious idea that it'd be good to strip
Log Message: --- Clean up after someone's curious idea that it'd be good to strip leading zeroes from the SQLSTATE codes. They're strings, people, not numbers. Modified Files: -- pgsql/doc/src/sgml: errcodes.sgml (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/errcodes.sgml.diff?r1=1.18&r2=1.19) ---(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: Clean up after someone's curious idea that it'd be good to strip
Log Message: --- Clean up after someone's curious idea that it'd be good to strip leading zeroes from the SQLSTATE codes. They're strings, people, not numbers. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: errcodes.sgml (r1.15.2.3 -> r1.15.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/errcodes.sgml.diff?r1=1.15.2.3&r2=1.15.2.4) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Code review for SELECT INTO STRICT patch: use saner choices of
Log Message: --- Code review for SELECT INTO STRICT patch: use saner choices of error SQLSTATEs, fix some documentation problems. Modified Files: -- pgsql/doc/src/sgml: errcodes.sgml (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/errcodes.sgml.diff?r1=1.19&r2=1.20) plpgsql.sgml (r1.96 -> r1.97) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plpgsql.sgml.diff?r1=1.96&r2=1.97) pgsql/src/include/utils: errcodes.h (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/errcodes.h.diff?r1=1.19&r2=1.20) pgsql/src/pl/plpgsql/src: gram.y (r1.92 -> r1.93) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.92&r2=1.93) pl_exec.c (r1.172 -> r1.173) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_exec.c.diff?r1=1.172&r2=1.173) plerrcodes.h (r1.8 -> r1.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/plerrcodes.h.diff?r1=1.8&r2=1.9) scan.l (r1.51 -> r1.52) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/scan.l.diff?r1=1.51&r2=1.52) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix a couple of obvious problems in DROP IF EXISTS patch.
Log Message: --- Fix a couple of obvious problems in DROP IF EXISTS patch. Modified Files: -- pgsql/src/backend/commands: aggregatecmds.c (r1.35 -> r1.36) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/aggregatecmds.c.diff?r1=1.35&r2=1.36) pgsql/src/backend/parser: gram.y (r2.546 -> r2.547) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.546&r2=2.547) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [COMMITTERS] pgsql: Fix a couple of obvious problems in DROP
Tom Lane wrote: Log Message: --- Fix a couple of obvious problems in DROP IF EXISTS patch. - n->missing_ok = + n->missing_ok = $3; Oops - sorry about that. I don't know how that one got past me - thanks for picking it up. cheers andrew ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgbuildfarm - client-code: Fix regex on status lines so it's not too
Log Message: --- Fix regex on status lines so it's not too greedy about the filename prefix. Modified Files: -- client-code: run_build.pl (r1.61 -> r1.62) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/run_build.pl.diff?r1=1.61&r2=1.62) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
