[COMMITTERS] pgsql: Update Chinese FAQ to fix XHTML format.

2005-06-03 Thread Bruce Momjian
Log Message: --- Update Chinese FAQ to fix XHTML format. Weiping (Laser) Tags: REL8_0_STABLE Modified Files: -- pgsql/doc: FAQ_chinese (r1.1.2.4 -> r1.1.2.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_chinese.diff?r1=1.1.2.4&r2=1.1.2.5

[COMMITTERS] pgsql: Update Chinese FAQ to fix XHTML format.

2005-06-03 Thread Bruce Momjian
Log Message: --- Update Chinese FAQ to fix XHTML format. Weiping (Laser) Modified Files: -- pgsql/doc: FAQ_chinese (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_chinese.diff?r1=1.4&r2=1.5) pgsql/doc/src/FAQ: FAQ_chine

[COMMITTERS] pgsql: Remove unused 'printCost' field from ExplainState, and simplify

2005-06-03 Thread Neil Conway
Log Message: --- Remove unused 'printCost' field from ExplainState, and simplify the code accordingly (this field was always initialized to true). Patch from Alvaro Herrera. Modified Files: -- pgsql/src/backend/commands: explain.c (r1.136 -> r1.137) (http:/

[COMMITTERS] pgsql: Revise handling of dropped columns in JOIN alias lists to avoid a

2005-06-03 Thread Tom Lane
Log Message: --- Revise handling of dropped columns in JOIN alias lists to avoid a performance problem pointed out by [EMAIL PROTECTED]: to wit, we were spending O(N^2) time to check dropped-ness in an N-deep join tree, even in the case where the tree was freshly constructed and couldn't po

[COMMITTERS] pgsql: Put back WAL TODO.detail entries.

2005-06-03 Thread Bruce Momjian
Log Message: --- Put back WAL TODO.detail entries. Modified Files: -- pgsql/doc/TODO.detail: wal (r1.5 -> r1.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/wal.diff?r1=1.5&r2=1.6) ---(end of broadcast)-

Re: [COMMITTERS] pgsql: Change CRCs in WAL records from 64bit to 32bit

2005-06-03 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > I have trimmed TODO.detail to remove the completed items. > > You removed far too much. OK, would you trim it from CVS and commit. I have restored it. -- Bruce Momjian| http://candle.pha.pa.us [email protected]

[COMMITTERS] pgsql: Remove because it is partly done and we might not want to go

2005-06-03 Thread Bruce Momjian
Log Message: --- Remove because it is partly done and we might not want to go farther: < * -Compress WAL entries [wal] Modified Files: -- pgsql/doc: TODO (r1.1543 -> r1.1544) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1543&r2=1.154

Re: [COMMITTERS] pgsql: Done: > * -Compress WAL entries [wal]

2005-06-03 Thread Bruce Momjian
Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > > Done: > >> * -Compress WAL entries [wal] > > It's not really "done" --- the ideas in the TODO file about using more > intelligent compression methods are still on the table. All I've done > is to nab some very low-hanging fruit. Yea

[COMMITTERS] pgsql: Just noticed that you can't Query-Cancel a long planner run,

2005-06-03 Thread Tom Lane
Log Message: --- Just noticed that you can't Query-Cancel a long planner run, because no part of the planner did CHECK_FOR_INTERRUPTS(). Add one in a suitably strategic spot. Modified Files: -- pgsql/src/backend/optimizer/util: pathnode.c (r1.120 -> r1.121)

[COMMITTERS] pgsql: Update Russian FAQ.

2005-06-03 Thread Bruce Momjian
Log Message: --- Update Russian FAQ. Viktor Vislobokov Modified Files: -- pgsql/doc: FAQ_russian (r1.26 -> r1.27) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_russian.diff?r1=1.26&r2=1.27) pgsql/doc/src/FAQ: FAQ_russian.html (r1.28

[COMMITTERS] pgsql: Update Russian FAQ.

2005-06-03 Thread Bruce Momjian
Log Message: --- Update Russian FAQ. Viktor Vislobokov Tags: REL8_0_STABLE Modified Files: -- pgsql/doc: FAQ (r1.292.4.12 -> r1.292.4.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.292.4.12&r2=1.292.4.13) FAQ_russian

Re: [COMMITTERS] pgsql: Change CRCs in WAL records from 64bit to 32bit

2005-06-03 Thread Tom Lane
Bruce Momjian writes: > I have trimmed TODO.detail to remove the completed items. You removed far too much. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.po

Re: [COMMITTERS] pgsql: Done: > * -Compress WAL entries [wal]

2005-06-03 Thread Tom Lane
[EMAIL PROTECTED] (Bruce Momjian) writes: > Done: >> * -Compress WAL entries [wal] It's not really "done" --- the ideas in the TODO file about using more intelligent compression methods are still on the table. All I've done is to nab some very low-hanging fruit. There's also the whole business o

[COMMITTERS] pgsql: Trim TODO.detail for wal completed items.

2005-06-03 Thread Bruce Momjian
Log Message: --- Trim TODO.detail for wal completed items. Modified Files: -- pgsql/doc/TODO.detail: wal (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/wal.diff?r1=1.4&r2=1.5) ---(end of broadcast)-

Re: [COMMITTERS] pgsql: Change CRCs in WAL records from 64bit to 32bit

2005-06-03 Thread Bruce Momjian
I have trimmed TODO.detail to remove the completed items. --- Tom Lane wrote: > Log Message: > --- > Change CRCs in WAL records from 64bit to 32bit for performance reasons. > Instead of a separate CRC on each backup

[COMMITTERS] pgsql: Done: > * -Compress WAL entries [wal]

2005-06-03 Thread Bruce Momjian
Log Message: --- Done: > * -Compress WAL entries [wal] Modified Files: -- pgsql/doc: TODO (r1.1542 -> r1.1543) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1542&r2=1.1543) pgsql/doc/src/FAQ: TODO.html (r1.49 -> r1.50)

[COMMITTERS] pgsql: Done: > * -Change WAL to use 32-bit CRC, for performance reasons

2005-06-03 Thread Bruce Momjian
Log Message: --- Done: > * -Change WAL to use 32-bit CRC, for performance reasons Modified Files: -- pgsql/doc: TODO (r1.1541 -> r1.1542) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1541&r2=1.1542) pgsql/doc/src/FAQ: TOD