[COMMITTERS] pgsql: Avoid scribbling on original parsetree during DECLARE CURSOR.
Log Message: --- Avoid scribbling on original parsetree during DECLARE CURSOR. This prevents problems when the DECLARE is in a portal and is executed repeatedly, as is possible in v3 protocol. Per analysis by Oliver Jowett, though I didn't use his patch exactly. Modified Files: -- pgsql/src/backend/commands: portalcmds.c (r1.36 -> r1.37) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/portalcmds.c.diff?r1=1.36&r2=1.37) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Avoid scribbling on original parsetree during DECLARE CURSOR.
Log Message: --- Avoid scribbling on original parsetree during DECLARE CURSOR. This prevents problems when the DECLARE is in a portal and is executed repeatedly, as is possible in v3 protocol. Per analysis by Oliver Jowett, though I didn't use his patch exactly. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/commands: portalcmds.c (r1.24 -> r1.24.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/portalcmds.c.diff?r1=1.24&r2=1.24.2.1) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[COMMITTERS] pgsql: Make pg_dumplo schema-aware.
Log Message: --- Make pg_dumplo schema-aware. Karel Zak Modified Files: -- pgsql/contrib/pg_dumplo: lo_export.c (r1.12 -> r1.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_dumplo/lo_export.c.diff?r1=1.12&r2=1.13) lo_import.c (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_dumplo/lo_import.c.diff?r1=1.10&r2=1.11) main.c (r1.21 -> r1.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_dumplo/main.c.diff?r1=1.21&r2=1.22) pg_dumplo.h (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_dumplo/pg_dumplo.h.diff?r1=1.10&r2=1.11) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Have initdb display relative paths to start postmaster if used to
Log Message: --- Have initdb display relative paths to start postmaster if used to invoke initdb, and display in a path-native way. Modified Files: -- pgsql/src/bin/initdb: initdb.c (r1.68 -> r1.69) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/initdb.c.diff?r1=1.68&r2=1.69) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Typo fixes.
Log Message: --- Typo fixes. Euler Taveira de Oliveira Modified Files: -- pgsql/doc: FAQ_brazilian (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_brazilian.diff?r1=1.2&r2=1.3) pgsql/doc/src/FAQ: FAQ_brazilian.html (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ_brazilian.html.diff?r1=1.2&r2=1.3) ---(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: Add: > * Auto-vacuum > o Move into the backend code > o Scan
Log Message: --- Add: > * Auto-vacuum > o Move into the backend code > o Scan the buffer cache to find free space or use background writer > o Use free-space map information to guide refilling Modified Files: -- pgsql/doc: TODO (r1.1401 -> r1.1402) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1401&r2=1.1402) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[COMMITTERS] pgsql: Add comment explaining possible compiler warning: /* *
Log Message: --- Add comment explaining possible compiler warning: /* * Some compilers with throw a warning knowing this test can never be * true because off_t can't exceed the compared maximum. */ if (th->fileLen > MAX_TAR_MEMBER_FILELEN) die_horribly(AH, modulename, "archive member too large for tar format\n"); Modified Files: -- pgsql/src/bin/pg_dump: pg_backup_tar.c (r1.45 -> r1.46) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_tar.c.diff?r1=1.45&r2=1.46) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[COMMITTERS] pgsql: Update Turkish FAQ.
Log Message: --- Update Turkish FAQ. Devrim GUNDUZ Modified Files: -- pgsql/doc: FAQ_turkish (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_turkish.diff?r1=1.4&r2=1.5) pgsql/doc/src/FAQ: FAQ_turkish.html (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ_turkish.html.diff?r1=1.4&r2=1.5) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Clean up initdb's error handling so that it prints something more
Log Message: --- Clean up initdb's error handling so that it prints something more useful than just \'failed\' when there's a problem. Per gripe from Chris Albertson. In an unrelated change, use VACUUM FULL; VACUUM FREEZE; rather than a single VACUUM FULL FREEZE command, to respond to my worries of a couple days ago about the reliability of doing this in one go. Modified Files: -- pgsql/src/bin/initdb: initdb.c (r1.69 -> r1.70) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/initdb.c.diff?r1=1.69&r2=1.70) ---(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: Add: < > * Allow cross-compiling by generating the zic database
Log Message: --- Add: < > * Allow cross-compiling by generating the zic database on the target system Modified Files: -- pgsql/doc: TODO (r1.1402 -> r1.1403) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1402&r2=1.1403) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
