[COMMITTERS] pgsql: Improve tab completion macro for default keywords.
Log Message: --- Improve tab completion macro for default keywords. Modified Files: -- pgsql/src/bin/psql: tab-complete.c (r1.147 -> r1.148) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.147&r2=1.148) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] npgsql - Npgsql: 2006-02-12 Francisco Figueiredo Jr.
Log Message: --- 2006-02-12 Francisco Figueiredo Jr. <[EMAIL PROTECTED]> * NpgsqlCommand.cs: [#1000546] prepare with wrong sql stmt hangs. Modified Files: -- Npgsql/src/Npgsql: NpgsqlCommand.cs (r1.88 -> r1.89) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql/src/Npgsql/NpgsqlCommand.cs.diff?r1=1.88&r2=1.89) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update release notes for 8.1.3.
Log Message: --- Update release notes for 8.1.3. Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.418 -> r1.419) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.418&r2=1.419) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Update release notes for 8.1.3.
Log Message: --- Update release notes for 8.1.3. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.400.2.18 -> r1.400.2.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.400.2.18&r2=1.400.2.19) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update for 8.1.3.
Log Message: --- Update for 8.1.3. Modified Files: -- pgsql/doc: FAQ (r1.374 -> r1.375) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.374&r2=1.375) pgsql/doc/src/FAQ: FAQ.html (r1.330 -> r1.331) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff?r1=1.330&r2=1.331) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Stamp 8.1.3, but exclude configure.in/configure change.
Log Message: --- Stamp 8.1.3, but exclude configure.in/configure change. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc: FAQ (r1.362.2.3 -> r1.362.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.362.2.3&r2=1.362.2.4) FAQ_AIX (r1.14.2.4 -> r1.14.2.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_AIX.diff?r1=1.14.2.4&r2=1.14.2.5) bug.template (r1.34.2.2 -> r1.34.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/bug.template.diff?r1=1.34.2.2&r2=1.34.2.3) pgsql/doc/src/FAQ: FAQ.html (r1.318.2.3 -> r1.318.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff?r1=1.318.2.3&r2=1.318.2.4) pgsql/src/include: pg_config.h.win32 (r1.22.2.4 -> r1.22.2.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config.h.win32.diff?r1=1.22.2.4&r2=1.22.2.5) pgsql/src/interfaces/libpq: libpq.rc.in (r1.3.2.2 -> r1.3.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq.rc.in.diff?r1=1.3.2.2&r2=1.3.2.3) pgsql/src/port: win32ver.rc (r1.6.2.2 -> r1.6.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/win32ver.rc.diff?r1=1.6.2.2&r2=1.6.2.3) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update release checlist.
Log Message: --- Update release checlist. Modified Files: -- pgsql/src/tools: RELEASE_CHANGES (r1.63 -> r1.64) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/RELEASE_CHANGES.diff?r1=1.63&r2=1.64) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Fix release markup.
Log Message: --- Fix release markup. Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.419 -> r1.420) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.419&r2=1.420) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Fix release markup.
Log Message: --- Fix release markup. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.400.2.19 -> r1.400.2.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.400.2.19&r2=1.400.2.20) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Update back branch release notes.
Log Message: --- Update back branch release notes. Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.420 -> r1.421) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.420&r2=1.421) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Update back branch release notes.
Log Message: --- Update back branch release notes. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.400.2.20 -> r1.400.2.21) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.400.2.20&r2=1.400.2.21) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Fix release item ordering.
Log Message: --- Fix release item ordering. Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.421 -> r1.422) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.421&r2=1.422) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix release item ordering.
Log Message: --- Fix release item ordering. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.400.2.21 -> r1.400.2.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.400.2.21&r2=1.400.2.22) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Update release notes for 2006-02-14 release
Log Message: --- Update release notes for 2006-02-14 release Tags: REL7_3_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.163.2.29 -> r1.163.2.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.163.2.29&r2=1.163.2.30) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update release notes for 2006-02-14 release
Log Message: --- Update release notes for 2006-02-14 release Tags: REL7_4_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.235.2.39 -> r1.235.2.40) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.235.2.39&r2=1.235.2.40) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update release notes for 2006-02-14 release
Log Message: --- Update release notes for 2006-02-14 release Tags: REL8_0_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.321.4.20 -> r1.321.4.21) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.321.4.20&r2=1.321.4.21) ---(end of broadcast)--- TIP 1: 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: Stamp releases for 2006-02-14 release
Log Message: --- Stamp releases for 2006-02-14 release Tags: REL7_3_STABLE Modified Files: -- pgsql/doc: bug.template (r1.21.2.14 -> r1.21.2.15) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/bug.template.diff?r1=1.21.2.14&r2=1.21.2.15) pgsql/src/include: pg_config.h.win32 (r1.8.2.13 -> r1.8.2.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config.h.win32.diff?r1=1.8.2.13&r2=1.8.2.14) pgsql/src/interfaces/libpq: libpq.rc (r1.9.2.13 -> r1.9.2.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq.rc.diff?r1=1.9.2.13&r2=1.9.2.14) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Stamp releases for 2006-02-14 release
Log Message: --- Stamp releases for 2006-02-14 release Tags: REL7_4_STABLE Modified Files: -- pgsql/doc: bug.template (r1.21.6.13 -> r1.21.6.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/bug.template.diff?r1=1.21.6.13&r2=1.21.6.14) pgsql/src/include: pg_config.h.win32 (r1.11.4.12 -> r1.11.4.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config.h.win32.diff?r1=1.11.4.12&r2=1.11.4.13) pgsql/src/interfaces/libpq: libpq.rc (r1.10.4.11 -> r1.10.4.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq.rc.diff?r1=1.10.4.11&r2=1.10.4.12) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Stamp releases for 2006-02-14 release
Log Message: --- Stamp releases for 2006-02-14 release Tags: REL8_0_STABLE Modified Files: -- pgsql/doc: bug.template (r1.26.4.8 -> r1.26.4.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/bug.template.diff?r1=1.26.4.8&r2=1.26.4.9) pgsql/src/include: pg_config.h.win32 (r1.21.4.7 -> r1.21.4.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config.h.win32.diff?r1=1.21.4.7&r2=1.21.4.8) pgsql/src/interfaces/libpq: libpq.rc.in (r1.2.4.8 -> r1.2.4.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq.rc.in.diff?r1=1.2.4.8&r2=1.2.4.9) pgsql/src/port: win32ver.rc (r1.5.4.6 -> r1.5.4.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/win32ver.rc.diff?r1=1.5.4.6&r2=1.5.4.7) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Stamp releases for 2006-02-14 release
Log Message: --- Stamp releases for 2006-02-14 release Tags: REL8_1_STABLE Modified Files: -- pgsql/doc: bug.template (r1.34.2.3 -> r1.34.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/bug.template.diff?r1=1.34.2.3&r2=1.34.2.4) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Update FAQ latest version
Log Message: --- Update FAQ latest version Tags: REL7_3_STABLE Modified Files: -- pgsql/doc: FAQ (r1.193.2.5 -> r1.193.2.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.193.2.5&r2=1.193.2.6) pgsql/doc/src/FAQ: FAQ.html (r1.163.2.6 -> r1.163.2.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff?r1=1.163.2.6&r2=1.163.2.7) ---(end of broadcast)--- TIP 1: 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: Update FAQ latest version
Log Message: --- Update FAQ latest version Tags: REL7_4_STABLE Modified Files: -- pgsql/doc: FAQ (r1.238.2.4 -> r1.238.2.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.238.2.4&r2=1.238.2.5) pgsql/doc/src/FAQ: FAQ.html (r1.195.2.5 -> r1.195.2.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff?r1=1.195.2.5&r2=1.195.2.6) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Update FAQ latest version
Log Message: --- Update FAQ latest version Tags: REL8_0_STABLE Modified Files: -- pgsql/doc: FAQ (r1.292.4.18 -> r1.292.4.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.292.4.18&r2=1.292.4.19) pgsql/doc/src/FAQ: FAQ.html (r1.248.4.19 -> r1.248.4.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff?r1=1.248.4.19&r2=1.248.4.20) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: > Actually, if you submit a patch that says either "SCROLL is the
Log Message: --- > Actually, if you submit a patch that says either "SCROLL is the default" > or "NO SCROLL is the default", it will be rejected as incorrect. The > reason is that the default behavior is different from either of these, > as is explained in the NOTES section. Ok, so *that's* where the bit about the query plan being simple enough. Based on that, ISTM that it should be premissable for us to decide that a cursor requiring a sort isn't "simple enough" to support SCROLL. In any case, here's a patch that makes the non-standard behavior easier for people to find. Jim C. Nasby Modified Files: -- pgsql/doc/src/sgml/ref: declare.sgml (r1.34 -> r1.35) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/declare.sgml.diff?r1=1.34&r2=1.35) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: > Actually, if you submit a patch that says either "SCROLL is the
Log Message: --- > Actually, if you submit a patch that says either "SCROLL is the default" > or "NO SCROLL is the default", it will be rejected as incorrect. The > reason is that the default behavior is different from either of these, > as is explained in the NOTES section. Ok, so *that's* where the bit about the query plan being simple enough. Based on that, ISTM that it should be premissable for us to decide that a cursor requiring a sort isn't "simple enough" to support SCROLL. In any case, here's a patch that makes the non-standard behavior easier for people to find. Jim C. Nasby Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml/ref: declare.sgml (r1.33 -> r1.33.6.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/declare.sgml.diff?r1=1.33&r2=1.33.6.1) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] python - pq: Make Startup message inherit from DictionaryType.
Log Message: --- Make Startup message inherit from DictionaryType. [Instead of delegating] Modified Files: -- pq/src: element3.py (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/element3.py.diff?r1=1.10&r2=1.11) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] python - pq: Update Startup related test.
Log Message: --- Update Startup related test. Modified Files: -- pq/test: element3.py (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/test/element3.py.diff?r1=1.5&r2=1.6) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Revert patch becaues of locking concerns: Allow ALTER TABLE ...
Log Message: --- Revert patch becaues of locking concerns: Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME Joachim Wieland Modified Files: -- pgsql/doc/src/sgml: ddl.sgml (r1.53 -> r1.54) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ddl.sgml.diff?r1=1.53&r2=1.54) pgsql/doc/src/sgml/ref: alter_index.sgml (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_index.sgml.diff?r1=1.7&r2=1.8) alter_table.sgml (r1.83 -> r1.84) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_table.sgml.diff?r1=1.83&r2=1.84) pgsql/src/backend/catalog: pg_constraint.c (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_constraint.c.diff?r1=1.29&r2=1.30) pg_depend.c (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_depend.c.diff?r1=1.18&r2=1.19) pgsql/src/backend/commands: alter.c (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/alter.c.diff?r1=1.16&r2=1.17) pgsql/src/backend/parser: gram.y (r2.528 -> r2.529) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.528&r2=2.529) pgsql/src/backend/tcop: utility.c (r1.251 -> r1.252) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/utility.c.diff?r1=1.251&r2=1.252) pgsql/src/include/catalog: dependency.h (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/dependency.h.diff?r1=1.19&r2=1.20) pg_constraint.h (r1.20 -> r1.21) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_constraint.h.diff?r1=1.20&r2=1.21) pgsql/src/test/regress/expected: alter_table.out (r1.91 -> r1.92) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/alter_table.out.diff?r1=1.91&r2=1.92) pgsql/src/test/regress/sql: alter_table.sql (r1.53 -> r1.54) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/alter_table.sql.diff?r1=1.53&r2=1.54) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Not done: > o %Allow ALTER TABLE ...
Log Message: --- Not done: > o %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME Modified Files: -- pgsql/doc: TODO (r1.1766 -> r1.1767) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1766&r2=1.1767) pgsql/doc/src/FAQ: TODO.html (r1.271 -> r1.272) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.271&r2=1.272) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] python - pq: No need for adding an extra __init__ layer anymore.
Log Message: --- No need for adding an extra __init__ layer anymore. Modified Files: -- pq/src: element3.py (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/element3.py.diff?r1=1.11&r2=1.12) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] python - pq: Get rid of the superfluous 'Ignition' message.
Log Message: --- Get rid of the superfluous 'Ignition' message. Instead, store the priming messages in the 'ignition' attribute. This helps to avoid the confusion that client3.Ignition created. (Also, 'PANIC' is also FATAL; we may get panic messages!) [Something more formal should probably be drawn; xact.ignition is fine for now] Modified Files: -- pq/src: client3.py (r1.13 -> r1.14) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/client3.py.diff?r1=1.13&r2=1.14) pq/test: client3.py (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/test/client3.py.diff?r1=1.7&r2=1.8) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update wording for 8.1.X, remove : This option can
Log Message: --- Update wording for 8.1.X, remove : This option can be set at server start or in the postgresql.conf configuration file. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.36.2.1 -> r1.36.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.36.2.1&r2=1.36.2.2) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Update README file.
Log Message: --- Update README file. Joshua D. Drake Modified Files: -- pgsql: README (r1.30 -> r1.31) (http://developer.postgresql.org/cvsweb.cgi/pgsql/README.diff?r1=1.30&r2=1.31) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] python - fe: Stop using the Ignition message and Fix B&Es performance
Log Message: --- Stop using the Ignition message and Fix B&Es performance issue. Fix the BindingsAndExecutings performance failures by making the message buffer large enough for all the B&E messages that would be returned by a transaction call. This makes the message writer write all 21 or so messages in one write as opposed to three (10 Bs, 10 Es, and one Flush) Update tests accordingly. Modified Files: -- fe/src: tracenull.py (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.diff?r1=1.6&r2=1.7) fe/test: qio.py (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/test/qio.py.diff?r1=1.1.1.1&r2=1.2) tracenull.py (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/test/tracenull.py.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Update README file.
Log Message: --- Update README file. Joshua D. Drake Tags: REL8_1_STABLE Modified Files: -- pgsql: README (r1.30 -> r1.30.6.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/README.diff?r1=1.30&r2=1.30.6.1) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Remove LEFT part of JOIN to pg_roles because of optimizer
Log Message: --- Remove LEFT part of JOIN to pg_roles because of optimizer limitation: > True, but they're not being used where you'd expect. This seems to be > something to do with the fact that it's not pg_authid which is being > accessed, but rather the view pg_roles. I looked into this and it seems the problem is that the view doesn't get flattened into the main query because of the has_nullable_targetlist limitation in prepjointree.c. That's triggered because pg_roles has ''::text AS rolpassword which isn't nullable, meaning it would produce wrong behavior if referenced above the outer join. Ultimately, the reason this is a problem is that the planner deals only in simple Vars while processing joins; it doesn't want to think about expressions. I'm starting to think that it may be time to fix this, because I've run into several related restrictions lately, but it seems like a nontrivial project. In the meantime, reducing the LEFT JOIN to pg_roles to a JOIN as per Peter's suggestion seems like the best short-term workaround. Modified Files: -- pgsql/src/bin/psql: describe.c (r1.131 -> r1.132) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/describe.c.diff?r1=1.131&r2=1.132) ---(end of broadcast)--- TIP 1: 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: Support "" for thousands separator and plus sign in to_char(),
Log Message: --- Support "" for thousands separator and plus sign in to_char(), per report from French Debian user. psql already handles "" fine. Modified Files: -- pgsql/src/backend/utils/adt: formatting.c (r1.104 -> r1.105) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c.diff?r1=1.104&r2=1.105) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: > I've now tested this patch at home w/ 8.2HEAD and it seems to
Log Message: --- > I've now tested this patch at home w/ 8.2HEAD and it seems to fix the > bug. I plan on testing it under 8.1.2 at work tommorow with > mod_auth_krb5, etc, and expect it'll work there. Assuming all goes > well and unless someone objects I'll forward the patch to -patches. > It'd be great to have this fixed as it'll allow us to use Kerberos to > authenticate to phppgadmin and other web-based tools which use > Postgres. While playing with this patch under 8.1.2 at home I discovered a mistake in how I manually applied one of the hunks to fe-auth.c. Basically, the base code had changed and so the patch needed to be modified slightly. This is because the code no longer either has a freeable pointer under 'name' or has 'name' as NULL. The attached patch correctly frees the string from pg_krb5_authname (where it had been strdup'd) if and only if pg_krb5_authname returned a string (as opposed to falling through and having name be set using name = pw->name;). Also added a comment to this effect. Please review. Stephen Frost ([EMAIL PROTECTED]) wrote: Modified Files: -- pgsql/src/interfaces/libpq: fe-auth.c (r1.110 -> r1.111) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-auth.c.diff?r1=1.110&r2=1.111) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Back out patch pending review.
Log Message: --- Back out patch pending review. --- > I've now tested this patch at home w/ 8.2HEAD and it seems to fix the > bug. I plan on testing it under 8.1.2 at work tommorow with > mod_auth_krb5, etc, and expect it'll work there. Assuming all goes > well and unless someone objects I'll forward the patch to -patches. > It'd be great to have this fixed as it'll allow us to use Kerberos to > authenticate to phppgadmin and other web-based tools which use > Postgres. While playing with this patch under 8.1.2 at home I discovered a mistake in how I manually applied one of the hunks to fe-auth.c. Basically, the base code had changed and so the patch needed to be modified slightly. This is because the code no longer either has a freeable pointer under 'name' or has 'name' as NULL. The attached patch correctly frees the string from pg_krb5_authname (where it had been strdup'd) if and only if pg_krb5_authname returned a string (as opposed to falling through and having name be set using name = pw->name;). Also added a comment to this effect. Please review. Stephen Frost ([EMAIL PROTECTED]) wrote: Modified Files: -- pgsql/src/interfaces/libpq: fe-auth.c (r1.111 -> r1.112) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-auth.c.diff?r1=1.111&r2=1.112) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [COMMITTERS] pgsql: > I've now tested this patch at home w/ 8.2HEAD
Patch backed out, needs review, is in queue now. --- Bruce Momjian wrote: > Log Message: > --- > > I've now tested this patch at home w/ 8.2HEAD and it seems to fix the > > bug. I plan on testing it under 8.1.2 at work tommorow with > > mod_auth_krb5, etc, and expect it'll work there. Assuming all goes > > well and unless someone objects I'll forward the patch to -patches. > > It'd be great to have this fixed as it'll allow us to use Kerberos to > > authenticate to phppgadmin and other web-based tools which use > > Postgres. > > While playing with this patch under 8.1.2 at home I discovered a > mistake in how I manually applied one of the hunks to fe-auth.c. > Basically, the base code had changed and so the patch needed to be > modified slightly. This is because the code no longer either has a > freeable pointer under 'name' or has 'name' as NULL. > > The attached patch correctly frees the string from pg_krb5_authname > (where it had been strdup'd) if and only if pg_krb5_authname returned > a string (as opposed to falling through and having name be set using > name = pw->name;). Also added a comment to this effect. > Please review. > > Stephen Frost ([EMAIL PROTECTED]) wrote: > > Modified Files: > -- > pgsql/src/interfaces/libpq: > fe-auth.c (r1.110 -> r1.111) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-auth.c.diff?r1=1.110&r2=1.111) > > ---(end of broadcast)--- > TIP 4: Have you searched our list archives? > >http://archives.postgresql.org > -- Bruce Momjian| http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] autodoc - autodoc: Display index information in HTML output.
Log Message: --- Display index information in HTML output. Modified Files: -- autodoc: html.tmpl (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/html.tmpl.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Fix broken markup.
Log Message: --- Fix broken markup. Modified Files: -- pgsql/doc/src/sgml/ref: declare.sgml (r1.35 -> r1.36) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/declare.sgml.diff?r1=1.35&r2=1.36) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix broken markup.
Log Message: --- Fix broken markup. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml/ref: declare.sgml (r1.33.6.1 -> r1.33.6.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/declare.sgml.diff?r1=1.33.6.1&r2=1.33.6.2) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Throw a warning rather than an error on invalid character from
Log Message: --- Throw a warning rather than an error on invalid character from UTF8 to Latin1, like we do for other Latin encodings. Modified Files: -- pgsql/src/backend/utils/mb/conversion_procs/utf8_and_iso8859_1: utf8_and_iso8859_1.c (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_iso8859_1/utf8_and_iso8859_1.c.diff?r1=1.13&r2=1.14) ---(end of broadcast)--- TIP 1: 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: Fix bug that allowed any logged-in user to SET ROLE to any other
Log Message: --- Fix bug that allowed any logged-in user to SET ROLE to any other database user id (CVE-2006-0553). Also fix related bug in SET SESSION AUTHORIZATION that allows unprivileged users to crash the server, if it has been compiled with Asserts enabled. The escalation-of-privilege risk exists only in 8.1.0-8.1.2. However, the Assert-crash risk exists in all releases back to 7.3. Thanks to Akio Ishida for reporting this problem. Modified Files: -- pgsql/src/backend/commands: variable.c (r1.115 -> r1.116) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/variable.c.diff?r1=1.115&r2=1.116) pgsql/src/backend/utils/mb: encnames.c (r1.27 -> r1.28) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/encnames.c.diff?r1=1.27&r2=1.28) pgsql/src/backend/utils/misc: guc.c (r1.310 -> r1.311) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.310&r2=1.311) pgsql/src/include/utils: guc_tables.h (r1.20 -> r1.21) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/guc_tables.h.diff?r1=1.20&r2=1.21) ---(end of broadcast)--- TIP 1: 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: Fix bug that allowed any logged-in user to SET ROLE to any other
Log Message: --- Fix bug that allowed any logged-in user to SET ROLE to any other database user id (CVE-2006-0553). Also fix related bug in SET SESSION AUTHORIZATION that allows unprivileged users to crash the server, if it has been compiled with Asserts enabled. The escalation-of-privilege risk exists only in 8.1.0-8.1.2. However, the Assert-crash risk exists in all releases back to 7.3. Thanks to Akio Ishida for reporting this problem. Tags: REL8_1_STABLE Modified Files: -- pgsql/src/backend/commands: variable.c (r1.114.2.1 -> r1.114.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/variable.c.diff?r1=1.114.2.1&r2=1.114.2.2) pgsql/src/backend/utils/mb: encnames.c (r1.26 -> r1.26.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/encnames.c.diff?r1=1.26&r2=1.26.2.1) pgsql/src/backend/utils/misc: guc.c (r1.299.2.1 -> r1.299.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.299.2.1&r2=1.299.2.2) pgsql/src/include/utils: guc_tables.h (r1.20 -> r1.20.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/guc_tables.h.diff?r1=1.20&r2=1.20.2.1) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Fix bug in SET SESSION AUTHORIZATION that allows unprivileged
Log Message: --- Fix bug in SET SESSION AUTHORIZATION that allows unprivileged users to crash the server, if it has been compiled with Asserts enabled (CVE-2006-0553). Thanks to Akio Ishida for reporting this problem. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/commands: variable.c (r1.105.4.2 -> r1.105.4.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/variable.c.diff?r1=1.105.4.2&r2=1.105.4.3) pgsql/src/backend/utils/mb: encnames.c (r1.22 -> r1.22.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/encnames.c.diff?r1=1.22&r2=1.22.4.1) pgsql/src/backend/utils/misc: guc.c (r1.252.4.2 -> r1.252.4.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.252.4.2&r2=1.252.4.3) pgsql/src/include/utils: guc_tables.h (r1.19 -> r1.19.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/guc_tables.h.diff?r1=1.19&r2=1.19.4.1) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Fix bug in SET SESSION AUTHORIZATION that allows unprivileged
Log Message: --- Fix bug in SET SESSION AUTHORIZATION that allows unprivileged users to crash the server, if it has been compiled with Asserts enabled (CVE-2006-0553). Thanks to Akio Ishida for reporting this problem. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/commands: variable.c (r1.88.2.2 -> r1.88.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/variable.c.diff?r1=1.88.2.2&r2=1.88.2.3) pgsql/src/backend/utils/mb: encnames.c (r1.17 -> r1.17.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/encnames.c.diff?r1=1.17&r2=1.17.4.1) pgsql/src/backend/utils/misc: guc.c (r1.164.2.3 -> r1.164.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.164.2.3&r2=1.164.2.4) pgsql/src/include/utils: guc_tables.h (r1.6 -> r1.6.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/guc_tables.h.diff?r1=1.6&r2=1.6.4.1) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix bug in SET SESSION AUTHORIZATION that allows unprivileged
Log Message: --- Fix bug in SET SESSION AUTHORIZATION that allows unprivileged users to crash the server, if it has been compiled with Asserts enabled (CVE-2006-0553). Thanks to Akio Ishida for reporting this problem. Tags: REL7_3_STABLE Modified Files: -- pgsql/src/backend/commands: variable.c (r1.71.2.3 -> r1.71.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/variable.c.diff?r1=1.71.2.3&r2=1.71.2.4) pgsql/src/backend/utils/mb: encnames.c (r1.10.2.1 -> r1.10.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/encnames.c.diff?r1=1.10.2.1&r2=1.10.2.2) pgsql/src/backend/utils/misc: guc.c (r1.99.2.5 -> r1.99.2.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.99.2.5&r2=1.99.2.6) ---(end of broadcast)--- TIP 1: 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: Update release notes.
Log Message: --- Update release notes. Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.422 -> r1.423) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.422&r2=1.423) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Update release notes.
Log Message: --- Update release notes. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.400.2.22 -> r1.400.2.23) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.400.2.22&r2=1.400.2.23) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Update release notes.
Log Message: --- Update release notes. Tags: REL8_0_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.321.4.21 -> r1.321.4.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.321.4.21&r2=1.321.4.22) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Update release notes.
Log Message: --- Update release notes. Tags: REL7_4_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.235.2.40 -> r1.235.2.41) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.235.2.40&r2=1.235.2.41) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update release notes.
Log Message: --- Update release notes. Tags: REL7_3_STABLE Modified Files: -- pgsql/doc/src/sgml: release.sgml (r1.163.2.30 -> r1.163.2.31) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.163.2.30&r2=1.163.2.31) ---(end of broadcast)--- TIP 1: 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: Stamp 8.1.3.
Log Message: --- Stamp 8.1.3. Tags: REL8_1_STABLE Modified Files: -- pgsql: configure.in (r1.431.2.7 -> r1.431.2.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.in.diff?r1=1.431.2.7&r2=1.431.2.8) configure (r1.461.2.7 -> r1.461.2.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.461.2.7&r2=1.461.2.8) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Stamp 8.0.7.
Log Message: --- Stamp 8.0.7. Tags: REL8_0_STABLE Modified Files: -- pgsql: configure.in (r1.398.4.10 -> r1.398.4.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.in.diff?r1=1.398.4.10&r2=1.398.4.11) configure (r1.424.4.11 -> r1.424.4.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.424.4.11&r2=1.424.4.12) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Stamp 7.4.12.
Log Message: --- Stamp 7.4.12. Tags: REL7_4_STABLE Modified Files: -- pgsql: configure.in (r1.301.2.19 -> r1.301.2.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.in.diff?r1=1.301.2.19&r2=1.301.2.20) configure (r1.310.2.22 -> r1.310.2.23) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.310.2.22&r2=1.310.2.23) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Stamp 7.3.14.
Log Message: --- Stamp 7.3.14. Tags: REL7_3_STABLE Modified Files: -- pgsql: configure.in (r1.217.2.22 -> r1.217.2.23) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.in.diff?r1=1.217.2.22&r2=1.217.2.23) configure (r1.226.2.24 -> r1.226.2.25) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.226.2.24&r2=1.226.2.25) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [COMMITTERS] pgsql: Update wording for 8.1.X, remove : This option can
[EMAIL PROTECTED] (Bruce Momjian) writes: > Log Message: > --- > Update wording for 8.1.X, remove : > This option can be set at server start or in the > postgresql.conf configuration file. It wasn't confusing, and now it's incorrect. If you didn't like the wording when I suggested it, why didn't you join that discussion? regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [COMMITTERS] pgsql: Update wording for 8.1.X, remove : This
Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > > Log Message: > > --- > > Update wording for 8.1.X, remove : > > > This option can be set at server start or in the > > postgresql.conf configuration file. > > It wasn't confusing, and now it's incorrect. > > If you didn't like the wording when I suggested it, why didn't you > join that discussion? This is only for the 8.1.X wording, not the newer HEAD wording. I thought the 8.1.X wording was old. Why is it wrong? Feel free to revert it. -- Bruce Momjian| http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [COMMITTERS] pgsql: Update wording for 8.1.X, remove : This
Bruce Momjian writes: > This is only for the 8.1.X wording, not the newer HEAD wording. I > thought the 8.1.X wording was old. Why is it wrong? Feel free to > revert it. Oh, my mistake, I was thinking you had reverted the newer wording. Still, it seems wrong to me, because omitting "only" essentially turns the statement into a no-op. We wouldn't bother to say anything if you could set the parameter whenever you wanted. We could back-patch the newer wording if you want a change. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Revert because C locale uses "" for thousands_sep, meaning "n/a",
Log Message: --- Revert because C locale uses "" for thousands_sep, meaning "n/a", while French uses "" for "don't want". Seems we have to keep the existing behavior. Modified Files: -- pgsql/src/backend/utils/adt: formatting.c (r1.105 -> r1.106) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c.diff?r1=1.105&r2=1.106) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [COMMITTERS] pgsql: Update wording for 8.1.X, remove : This
Tom Lane wrote: > Bruce Momjian writes: > > This is only for the 8.1.X wording, not the newer HEAD wording. I > > thought the 8.1.X wording was old. Why is it wrong? Feel free to > > revert it. > > Oh, my mistake, I was thinking you had reverted the newer wording. > Still, it seems wrong to me, because omitting "only" essentially > turns the statement into a no-op. We wouldn't bother to say anything > if you could set the parameter whenever you wanted. > > We could back-patch the newer wording if you want a change. I only know the person was confused by the wording "Only X or Y" when X and Y are fairly complex phrases, so I just removed "only". I just said "X or Y", which seems to still cover it. Again, adjust however you wish. -- Bruce Momjian| http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: 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] autodoc - autodoc: Add in very simple inheritance documentation.
Log Message: --- Add in very simple inheritance documentation. Templates other than HTML need to be updated. Remove support for PostgreSQL 7.1 and 7.2. Continues to support 7.3 and later. Modified Files: -- autodoc: html.tmpl (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/html.tmpl.diff?r1=1.2&r2=1.3) postgresql_autodoc.pl (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/postgresql_autodoc.pl.diff?r1=1.11&r2=1.12) regressdatabase.sql (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/regressdatabase.sql.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Add: > > o Allow pg_hba.conf to specify host names along with
Log Message: --- Add: > > o Allow pg_hba.conf to specify host names along with IP addresses > > Host name lookup could occur when the postmaster reads the > pg_hba.conf file, or when the backend starts. Another > solution would be to reverse lookup the connection IP and > check that hostname against the host names in pg_hba.conf. > We could also then check that the host name maps to the IP > address. Modified Files: -- pgsql/doc: TODO (r1.1767 -> r1.1768) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1767&r2=1.1768) pgsql/doc/src/FAQ: TODO.html (r1.272 -> r1.273) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.272&r2=1.273) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] python - pq: A PANIC is also fatal.
Log Message: --- A PANIC is also fatal. Modified Files: -- pq/src: client3.py (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/client3.py.diff?r1=1.14&r2=1.15) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
