[COMMITTERS] pgsql: Trivial markup improvement.

2005-06-06 Thread Tom Lane
Log Message: --- Trivial markup improvement. Modified Files: -- pgsql/doc/src/sgml: func.sgml (r1.250 -> r1.251) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.250&r2=1.251) ---(end of broadcast)-

[COMMITTERS] pgsql: Update Hungarian FAQ and add an HTML version.

2005-06-06 Thread Bruce Momjian
Log Message: --- Update Hungarian FAQ and add an HTML version. Laszlo Hornyak Modified Files: -- pgsql/doc: FAQ_hungarian (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_hungarian.diff?r1=1.3&r2=1.4) Added Files: --- p

[COMMITTERS] pgsql: Remove the mostly-stubbed-out-anyway support routines for WAL

2005-06-06 Thread Tom Lane
Log Message: --- Remove the mostly-stubbed-out-anyway support routines for WAL UNDO. That code is never going to be used in the foreseeable future, and where it's more than a stub it's making the redo routines harder to read. Modified Files: -- pgsql/src/backend/access/gist

[COMMITTERS] pgsql: Modify XLogInsert API to make callers specify whether pages to be

2005-06-06 Thread Tom Lane
Log Message: --- Modify XLogInsert API to make callers specify whether pages to be backed up have the standard layout with unused space between pd_lower and pd_upper. When this is set, XLogInsert will omit the unused space without bothering to scan it to see if it's zero. That saves time i

[COMMITTERS] pgsql: Add: > * Fix incorrect rtree results due to wrong assumptions

2005-06-06 Thread Bruce Momjian
Log Message: --- Add: > * Fix incorrect rtree results due to wrong assumptions about "over" > operator semantics [rtree] Modified Files: -- pgsql/doc: TODO (r1.1552 -> r1.1553) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1552&r2=

[COMMITTERS] pgsql: Add rtee box index discussion.

2005-06-06 Thread Bruce Momjian
Log Message: --- Add rtee box index discussion. Added Files: --- pgsql/doc/TODO.detail: rtree (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/rtree?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast

[COMMITTERS] pgsql: Ipcrm -> ipcclean in error message:

2005-06-06 Thread Bruce Momjian
Log Message: --- Ipcrm -> ipcclean in error message: --- While playing around, I got the following error message: -- FATAL: pre-existing shared memory block (key 5432001, ID 90898435) is still in use HINT: If you'r

[COMMITTERS] pgsql: Update text for RESET CONNECTION: < all temporary tables,

2005-06-06 Thread Bruce Momjian
Log Message: --- Update text for RESET CONNECTION: < all temporary tables, removal of any NOTIFYs, cursors, prepared < queries(?), currval()s, etc. This could be used for connection pooling. < We could also change RESET ALL to have this functionality. > temporary tables, removin

[COMMITTERS] pgsql: Add support for an optional INTO clause to PL/PgSQL's EXECUTE

2005-06-06 Thread Neil Conway
Log Message: --- Add support for an optional INTO clause to PL/PgSQL's EXECUTE command. This allows the result of executing a SELECT to be assigned to a row variable, record variable, or list of scalars. Docs and regression tests updated. Per Pavel Stehule, improvements and cleanup by Neil

Re: [COMMITTERS] pgsql: Ipcrm -> ipcclean in error message:

2005-06-06 Thread Tom Lane
[EMAIL PROTECTED] (Bruce Momjian) writes: > Ipcrm -> ipcclean in error message: Are you kidding? ipcclean is an unportable, poorly-tested hack. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at

Re: [COMMITTERS] pgsql: Ipcrm -> ipcclean in error message:

2005-06-06 Thread Bruce Momjian
Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > > Ipcrm -> ipcclean in error message: > > Are you kidding? ipcclean is an unportable, poorly-tested hack. No, I am not kidding. Should we not be distributing it? It seems strange no to recommend a tool we distribute. -- Bruce Mo