[COMMITTERS] pgsql: Add some links to the CREATE FUNCTION reference page when

2005-05-19 Thread Neil Conway
Log Message: --- Add some links to the CREATE FUNCTION reference page when describing function definition for particular PLs. Original patch from David Fetter, editorializing by Neil Conway. Modified Files: -- pgsql/doc/src/sgml: plperl.sgml (r2.39 -> r2.40)

[COMMITTERS] pgsql: Make the CREATE RULE syntax description in rules.sgml more

2005-05-19 Thread Neil Conway
Log Message: --- Make the CREATE RULE syntax description in rules.sgml more consistent with the syntax description in the CREATE RULE reference page. From Kris Jurka. Modified Files: -- pgsql/doc/src/sgml: rules.sgml (r1.41 -> r1.42) (http://developer.postg

[COMMITTERS] pgsql: Implement md5(bytea), update regression tests and documentation.

2005-05-19 Thread Neil Conway
Log Message: --- Implement md5(bytea), update regression tests and documentation. Patch from Abhijit Menon-Sen, minor editorialization from Neil Conway. Also, improve md5(text) to allocate a constant-sized buffer on the stack rather than via palloc. Catalog version bumped. Modified Files:

[COMMITTERS] pgsql: Make a comment pgindent-proof, per suggestion from Alvaro.

2005-05-19 Thread Tom Lane
Log Message: --- Make a comment pgindent-proof, per suggestion from Alvaro. Modified Files: -- pgsql/src/backend/access/transam: xact.c (r1.201 -> r1.202) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xact.c.diff?r1=1.201&r2=1

Re: [COMMITTERS] pgsql: Split the shared-memory array of PGPROC pointers out of the

2005-05-19 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Excellent. May I suggest the following so pgindent does not mess up > this comment: Done, although I think it may not be necessary anymore. pgindent seems less eager to reformat comments than it once was. (Bruce, any info on that?)

[COMMITTERS] pgsql: Update comment that I missed the first time around.

2005-05-19 Thread Tom Lane
Log Message: --- Update comment that I missed the first time around. Modified Files: -- pgsql/src/backend/storage/ipc: procarray.c (r1.1 -> r1.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/procarray.c.diff?r1=1.1&r2=1.2)

[COMMITTERS] pgsql: Factor out lock cleanup code that is needed in several places in

2005-05-19 Thread Tom Lane
Log Message: --- Factor out lock cleanup code that is needed in several places in lock.c. Also, remove the rather useless return value of LockReleaseAll. Change response to detection of corruption in the shared lock tables to PANIC, since that is the only way of cleaning up fully. Original

Re: [COMMITTERS] pgsql: Split the shared-memory array of PGPROC pointers out of the

2005-05-19 Thread Alvaro Herrera
On Thu, May 19, 2005 at 06:35:48PM -0300, Tom Lane wrote: > Log Message: > --- > Split the shared-memory array of PGPROC pointers out of the sinval > communication structure, and make it its own module with its own lock. > This should reduce contention at least a little, and it definitely m

[COMMITTERS] pgsql: Split the shared-memory array of PGPROC pointers out of the

2005-05-19 Thread Tom Lane
Log Message: --- Split the shared-memory array of PGPROC pointers out of the sinval communication structure, and make it its own module with its own lock. This should reduce contention at least a little, and it definitely makes the code seem cleaner. Per my recent proposal. Modified Files

[COMMITTERS] pgbuildfarm - client-code: report the steps the script actually passed

2005-05-19 Thread User Andrewd
Log Message: --- report the steps the script actually passed - only report the PLCheck step if one or more PLs was actually checked. Modified Files: -- client-code: run_build.pl (r1.25 -> r1.26) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/clie