[COMMITTERS] pllolcode - pllolcode: Make basic IM IN YR loops work.

2008-04-30 Thread User Eggyknap
Log Message: --- Make basic IM IN YR loops work. All loops (right now) are infinite, unless you explicitly call GTFO Modified Files: -- pllolcode: DOC (r1.24 -> r1.25) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/pllolcode/DOC.diff?r1=1.24&r2=1.2

[COMMITTERS] pllolcode - pllolcode: Make GTFO handling in WTF? blocks affect external

2008-04-30 Thread User Eggyknap
Log Message: --- Make GTFO handling in WTF? blocks affect external loops, etc. Modified Files: -- pllolcode: gram.y (r1.30 -> r1.31) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/pllolcode/gram.y.diff?r1=1.30&r2=1.31) -- Sent via pgsql-committers

[COMMITTERS] pllolcode - pllolcode: Declare iminyrNode(lolNode*) and squash a warning

2008-04-30 Thread User Eggyknap
Log Message: --- Declare iminyrNode(lolNode*) and squash a warning Modified Files: -- pllolcode: gram.y (r1.29 -> r1.30) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/pllolcode/gram.y.diff?r1=1.29&r2=1.30) -- Sent via pgsql-committers mailing lis

[COMMITTERS] pgsql: Add example showing how to remove a password from a role.

2008-04-30 Thread Alvaro Herrera
Log Message: --- Add example showing how to remove a password from a role. Andreas Scherbaum Modified Files: -- pgsql/doc/src/sgml/ref: alter_role.sgml (r1.9 -> r1.10) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_role.sgml?r1=1.9&

[COMMITTERS] pgsql: Fix nodeTidscan.c to not trigger an error if the block number

2008-04-30 Thread Tom Lane
Log Message: --- Fix nodeTidscan.c to not trigger an error if the block number portion of a user-supplied TID is out of range for the relation. This is needed to preserve compatibility with our pre-8.3 behavior, and it is sensible anyway since if the query were implemented by brute force r

[COMMITTERS] pgsql: Fix nodeTidscan.c to not trigger an error if the block number

2008-04-30 Thread Tom Lane
Log Message: --- Fix nodeTidscan.c to not trigger an error if the block number portion of a user-supplied TID is out of range for the relation. This is needed to preserve compatibility with our pre-8.3 behavior, and it is sensible anyway since if the query were implemented by brute force r