[COMMITTERS] pgsql: Spell DELIMITER correctly, per Seamus Dean.
Log Message: --- Spell DELIMITER correctly, per Seamus Dean. Modified Files: -- pgsql/src/bin/psql: tab-complete.c (r1.125 -> r1.126) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.125&r2=1.126) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Spell DELIMITER correctly, per Seamus Dean.
Log Message: --- Spell DELIMITER correctly, per Seamus Dean. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/bin/psql: tab-complete.c (r1.120 -> r1.120.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.120&r2=1.120.4.1) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Preliminary release notes for 8.0.3, 7.4.8, 7.3.10.
Log Message: --- Preliminary release notes for 8.0.3, 7.4.8, 7.3.10. Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.333 -> r1.334) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.333&r2=1.334) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Use postmaster_is_alive() check in pg_ctl restart as well as
Log Message: --- Use postmaster_is_alive() check in pg_ctl restart as well as pg_ctl status, so that restart doesn't fail when old postmaster died unbetimes. Modified Files: -- pgsql/src/bin/pg_ctl: pg_ctl.c (r1.56 -> r1.57) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_ctl/pg_ctl.c.diff?r1=1.56&r2=1.57) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Use postmaster_is_alive() check in pg_ctl restart as well as
Log Message: --- Use postmaster_is_alive() check in pg_ctl restart as well as pg_ctl status, so that restart doesn't fail when old postmaster died unbetimes. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/bin/pg_ctl: pg_ctl.c (r1.53.4.1 -> r1.53.4.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_ctl/pg_ctl.c.diff?r1=1.53.4.1&r2=1.53.4.2) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] pgsql: Allow implicit cast from any named composite type to RECORD.
Log Message: --- Allow implicit cast from any named composite type to RECORD. At the moment this has no particular use except to allow table rows to be passed to record_out(), but that case seems to be useful in itself per recent example from Elein. Further down the road we could look at letting PL functions be declared to accept RECORD parameters. Modified Files: -- pgsql/src/backend/parser: parse_coerce.c (r2.127 -> r2.128) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_coerce.c.diff?r1=2.127&r2=2.128) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Typo fix, Dave Held
Log Message: --- Typo fix, Dave Held Modified Files: -- pgsql/doc: FAQ (r1.349 -> r1.350) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.349&r2=1.350) pgsql/doc/src/FAQ: FAQ.html (r1.306 -> r1.307) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff?r1=1.306&r2=1.307) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Update "control" item.
Log Message: --- Update "control" item. Rosser Schwarz Modified Files: -- pgsql/doc: FAQ (r1.350 -> r1.351) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.350&r2=1.351) pgsql/doc/src/FAQ: FAQ.html (r1.307 -> r1.308) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff?r1=1.307&r2=1.308) ---(end of broadcast)--- TIP 3: 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: Adjust nodeBitmapIndexscan to keep the target index opened from
Log Message: --- Adjust nodeBitmapIndexscan to keep the target index opened from plan startup to end, rather than re-opening it in each MultiExecBitmapIndexScan call. I had foolishly thought that opening/closing wouldn't be much more expensive than a rescan call, but that was sheer brain fade. This seems to fix about half of the performance lossage reported by Sergey Koposov. I'm still not sure where the other half went. Modified Files: -- pgsql/src/backend/executor: nodeBitmapIndexscan.c (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeBitmapIndexscan.c.diff?r1=1.7&r2=1.8) pgsql/src/include/nodes: execnodes.h (r1.130 -> r1.131) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/execnodes.h.diff?r1=1.130&r2=1.131) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
