Re: [COMMITTERS] pgsql: Add INET/CIDR operators: and, or, not, plus int8, minus int8, and
[EMAIL PROTECTED] (Bruce Momjian) writes: > Log Message: > --- > Add INET/CIDR operators: and, or, not, plus int8, minus int8, and inet > minus inet. Shouldn't this commit have included a catversion.h bump? regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Update catalog version for INET additions.
Log Message: --- Update catalog version for INET additions. Modified Files: -- pgsql/src/include/catalog: catversion.h (r1.313 -> r1.314) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h.diff?r1=1.313&r2=1.314) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [COMMITTERS] pgsql: Add INET/CIDR operators: and, or, not, plus
Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > > Log Message: > > --- > > Add INET/CIDR operators: and, or, not, plus int8, minus int8, and inet > > minus inet. > > Shouldn't this commit have included a catversion.h bump? Yes, just done. I mentioned it in the posting but forgot to do it on commit. -- 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] pgsql: Allow VACUUM to complete faster by avoiding scanning the indexes
Log Message: --- Allow VACUUM to complete faster by avoiding scanning the indexes when no rows were removed from the heap by the VACUUM. Simon Riggs Modified Files: -- pgsql/src/backend/access/gist: gistvacuum.c (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistvacuum.c.diff?r1=1.11&r2=1.12) pgsql/src/backend/access/hash: hash.c (r1.83 -> r1.84) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hash.c.diff?r1=1.83&r2=1.84) pgsql/src/backend/access/index: indexam.c (r1.87 -> r1.88) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/index/indexam.c.diff?r1=1.87&r2=1.88) pgsql/src/backend/access/nbtree: nbtree.c (r1.136 -> r1.137) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.136&r2=1.137) pgsql/src/backend/commands: vacuum.c (r1.321 -> r1.322) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.321&r2=1.322) vacuumlazy.c (r1.63 -> r1.64) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.63&r2=1.64) pgsql/src/include/access: genam.h (r1.54 -> r1.55) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/genam.h.diff?r1=1.54&r2=1.55) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [COMMITTERS] pgsql: Allow VACUUM to complete faster by avoiding scanning the indexes
[EMAIL PROTECTED] (Bruce Momjian) writes: > Log Message: > --- > Allow VACUUM to complete faster by avoiding scanning the indexes when no > rows were removed from the heap by the VACUUM. I didn't see that go by, and request it be reverted. This has consequences that I do not think Simon understands. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Revert based on Tom's recommendation: > Allow VACUUM to complete
Log Message: --- Revert based on Tom's recommendation: > Allow VACUUM to complete faster by avoiding scanning the indexes when no > rows were removed from the heap by the VACUUM. Modified Files: -- pgsql/src/backend/access/gist: gistvacuum.c (r1.12 -> r1.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistvacuum.c.diff?r1=1.12&r2=1.13) pgsql/src/backend/access/hash: hash.c (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hash.c.diff?r1=1.84&r2=1.85) pgsql/src/backend/access/index: indexam.c (r1.88 -> r1.89) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/index/indexam.c.diff?r1=1.88&r2=1.89) pgsql/src/backend/access/nbtree: nbtree.c (r1.137 -> r1.138) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.137&r2=1.138) pgsql/src/backend/commands: vacuum.c (r1.322 -> r1.323) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.322&r2=1.323) vacuumlazy.c (r1.64 -> r1.65) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.64&r2=1.65) pgsql/src/include/access: genam.h (r1.55 -> r1.56) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/genam.h.diff?r1=1.55&r2=1.56) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgfouine - pgfouine: PHP 5.1 fixes
Log Message: --- PHP 5.1 fixes Modified Files: -- pgfouine/include/reporting: HtmlWithGraphsReportAggregator.class.php (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/HtmlWithGraphsReportAggregator.class.php.diff?r1=1.2&r2=1.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] pgfouine - pgfouine: PHP 5.1 fixes
Log Message: --- PHP 5.1 fixes Modified Files: -- pgfouine/include/listeners/error: NormalizedErrorsListener.class.php (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/listeners/error/NormalizedErrorsListener.class.php.diff?r1=1.4&r2=1.5) pgfouine/include/listeners/query: SlowestQueriesListener.class.php (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/listeners/query/SlowestQueriesListener.class.php.diff?r1=1.5&r2=1.6) NormalizedQueriesListener.class.php (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/listeners/query/NormalizedQueriesListener.class.php.diff?r1=1.8&r2=1.9) pgfouine/include/lib: common.lib.php (r1.13 -> r1.14) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/lib/common.lib.php.diff?r1=1.13&r2=1.14) pgfouine/include/reporting: reports.lib.php (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/reports.lib.php.diff?r1=1.10&r2=1.11) pgfouine/include/postgresql/lines: PostgreSQLDurationLine.class.php (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/lines/PostgreSQLDurationLine.class.php.diff?r1=1.6&r2=1.7) pgfouine/include/postgresql/parsers: PostgreSQLParser.class.php (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/parsers/PostgreSQLParser.class.php.diff?r1=1.11&r2=1.12) SyslogPostgreSQLParser.class.php (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/postgresql/parsers/SyslogPostgreSQLParser.class.php.diff?r1=1.7&r2=1.8) pgfouine/include: GenericLogReader.class.php (r1.18 -> r1.19) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/GenericLogReader.class.php.diff?r1=1.18&r2=1.19) LogStream.class.php (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/LogStream.class.php.diff?r1=1.10&r2=1.11) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgfouine - pgfouine: changed error_reporting level for php 4.4
Log Message: --- changed error_reporting level for php 4.4 Modified Files: -- pgfouine: pgfouine.php (r1.24 -> r1.25) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/pgfouine.php.diff?r1=1.24&r2=1.25) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgfouine - pgfouine: let's release 0.4.99 for PHP 5.1 users
Log Message: --- let's release 0.4.99 for PHP 5.1 users Modified Files: -- pgfouine: pgfouine.spec (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/pgfouine.spec.diff?r1=1.4&r2=1.5) pgfouine.php (r1.25 -> r1.26) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/pgfouine.php.diff?r1=1.25&r2=1.26) ChangeLog (r1.15 -> r1.16) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/ChangeLog.diff?r1=1.15&r2=1.16) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgfouine - www: New Directory
Update of /cvsroot/pgfouine/www/reports In directory pgfoundry.org:/tmp/cvs-serv93976/reports Log Message: Directory /cvsroot/pgfouine/www/reports added to the repository ---(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] pgfouine - www: updated website
Log Message: --- updated website Modified Files: -- www: tutorial.html (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/tutorial.html.diff?r1=1.1&r2=1.2) reports.html (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports.html.diff?r1=1.1&r2=1.2) index.html (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/index.html.diff?r1=1.7&r2=1.8) Added Files: --- www/reports: sample_reports.html (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_reports.html?rev=1.1&content-type=text/x-cvsweb-markup) sample_default.html (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_default.html?rev=1.1&content-type=text/x-cvsweb-markup) sample_examples.html (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_examples.html?rev=1.1&content-type=text/x-cvsweb-markup) sample_graphs_hourly_write_queries.png (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_graphs_hourly_write_queries.png?rev=1.1&content-type=text/x-cvsweb-markup) sample_graphs_hourly_select_queries.png (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_graphs_hourly_select_queries.png?rev=1.1&content-type=text/x-cvsweb-markup) sample_graphs.html (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_graphs.html?rev=1.1&content-type=text/x-cvsweb-markup) sample_only_select.html (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_only_select.html?rev=1.1&content-type=text/x-cvsweb-markup) sample_errors.html (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports/sample_errors.html?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgfouine - www:
Log Message: --- Modified Files: -- www: index.html (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/index.html.diff?r1=1.8&r2=1.9) ---(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] pgfouine - www: fixed last example
Log Message: --- fixed last example Modified Files: -- www: reports.html (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/reports.html.diff?r1=1.2&r2=1.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] pgfouine - www: reorganized samples
Log Message: --- reorganized samples Removed Files: - www: sample_only_select.html (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/sample_only_select.html) sample_default.html (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/sample_default.html) sample_reports.html (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/sample_reports.html) sample_examples.html (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/sample_examples.html) sample_errors.html (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/sample_errors.html) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [COMMITTERS] pgsql: Add INET/CIDR operators: and, or, not, plus
Actually this patch has got some worse problems:
regression=# select '127.0.0.1'::inet + 256;
?column?
---
127.0.2.1
(1 row)
which is wrong; if that's not obvious try
regression=# select ('127.0.0.1'::inet + 256) - 256;
?column?
---
127.0.1.1
(1 row)
or
regression=# select '127::2'::inet - ('127::2'::inet - 256);
?column?
--
-65280
(1 row)
I think the overflow checks are wrong, and the current buildfarm
results say there's a portability problem too. Working on it now...
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
[COMMITTERS] pgsql: Fix incorrect addition, subtraction, and overflow checking in new
Log Message: --- Fix incorrect addition, subtraction, and overflow checking in new inet operators. Modified Files: -- pgsql/src/backend/utils/adt: network.c (r1.64 -> r1.65) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/network.c.diff?r1=1.64&r2=1.65) pgsql/src/include/catalog: pg_proc.h (r1.395 -> r1.396) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h.diff?r1=1.395&r2=1.396) pgsql/src/test/regress/expected: inet.out (r1.20 -> r1.21) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/inet.out.diff?r1=1.20&r2=1.21) pgsql/src/test/regress/sql: inet.sql (r1.12 -> r1.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/inet.sql.diff?r1=1.12&r2=1.13) ---(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: o Improve psql's handling of multi-line statements Currently,
Log Message: --- o Improve psql's handling of multi-line statements Currently, while \e saves a single statement as one entry, interactive statements are saved one line at a time. Ideally all statements would be saved like \e does. Sergey E. Koposov Modified Files: -- pgsql/src/bin/psql: help.c (r1.106 -> r1.107) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/help.c.diff?r1=1.106&r2=1.107) input.c (r1.46 -> r1.47) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/input.c.diff?r1=1.46&r2=1.47) input.h (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/input.h.diff?r1=1.23&r2=1.24) mainloop.c (r1.69 -> r1.70) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/mainloop.c.diff?r1=1.69&r2=1.70) prompt.c (r1.41 -> r1.42) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/prompt.c.diff?r1=1.41&r2=1.42) tab-complete.c (r1.144 -> r1.145) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.144&r2=1.145) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Done: > o -Allow ALTER TABLE ...
Log Message: --- Done: > o -Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME Modified Files: -- pgsql/doc: TODO (r1.1762 -> r1.1763) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1762&r2=1.1763) pgsql/doc/src/FAQ: TODO.html (r1.267 -> r1.268) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.267&r2=1.268) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Allow ALTER TABLE ...
Log Message: --- Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME Joachim Wieland Modified Files: -- pgsql/doc/src/sgml: ddl.sgml (r1.52 -> r1.53) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ddl.sgml.diff?r1=1.52&r2=1.53) pgsql/doc/src/sgml/ref: alter_index.sgml (r1.6 -> r1.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_index.sgml.diff?r1=1.6&r2=1.7) alter_table.sgml (r1.82 -> r1.83) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_table.sgml.diff?r1=1.82&r2=1.83) pgsql/src/backend/catalog: pg_constraint.c (r1.28 -> r1.29) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_constraint.c.diff?r1=1.28&r2=1.29) pg_depend.c (r1.17 -> r1.18) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_depend.c.diff?r1=1.17&r2=1.18) pgsql/src/backend/commands: alter.c (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/alter.c.diff?r1=1.15&r2=1.16) pgsql/src/backend/parser: gram.y (r2.526 -> r2.527) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.526&r2=2.527) pgsql/src/backend/tcop: utility.c (r1.250 -> r1.251) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/utility.c.diff?r1=1.250&r2=1.251) pgsql/src/include/catalog: dependency.h (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/dependency.h.diff?r1=1.18&r2=1.19) pg_constraint.h (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_constraint.h.diff?r1=1.19&r2=1.20) pgsql/src/test/regress/expected: alter_table.out (r1.90 -> r1.91) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/alter_table.out.diff?r1=1.90&r2=1.91) pgsql/src/test/regress/sql: alter_table.sql (r1.52 -> r1.53) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/alter_table.sql.diff?r1=1.52&r2=1.53) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Done: < o Improve psql's handling of multi-line statements > o
Log Message: --- Done: < o Improve psql's handling of multi-line statements > o -Improve psql's handling of multi-line statements Modified Files: -- pgsql/doc: TODO (r1.1761 -> r1.1762) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1761&r2=1.1762) pgsql/doc/src/FAQ: TODO.html (r1.266 -> r1.267) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.266&r2=1.267) ---(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: Skip ambulkdelete scan if there's nothing to delete and the index
Log Message: --- Skip ambulkdelete scan if there's nothing to delete and the index is not partial. None of the existing AMs do anything useful except counting tuples when there's nothing to delete, and we can get a tuple count from the heap as long as it's not a partial index. (hash actually can skip anyway because it maintains a tuple count in the index metapage.) GIST is not currently able to exploit this optimization because, due to failure to index NULLs, GIST is always effectively partial. Possibly we should fix that sometime. Simon Riggs w/ some review by Tom Lane. Modified Files: -- pgsql/doc/src/sgml: indexam.sgml (r2.7 -> r2.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/indexam.sgml.diff?r1=2.7&r2=2.8) pgsql/src/backend/access/gist: gistvacuum.c (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistvacuum.c.diff?r1=1.13&r2=1.14) pgsql/src/backend/access/hash: hash.c (r1.85 -> r1.86) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hash.c.diff?r1=1.85&r2=1.86) pgsql/src/backend/access/index: indexam.c (r1.89 -> r1.90) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/index/indexam.c.diff?r1=1.89&r2=1.90) pgsql/src/backend/access/nbtree: nbtree.c (r1.138 -> r1.139) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.138&r2=1.139) pgsql/src/backend/commands: vacuum.c (r1.323 -> r1.324) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.323&r2=1.324) vacuumlazy.c (r1.65 -> r1.66) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.65&r2=1.66) pgsql/src/include/access: genam.h (r1.56 -> r1.57) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/genam.h.diff?r1=1.56&r2=1.57) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Actually there's a better way to do this, which is to count
Log Message: --- Actually there's a better way to do this, which is to count tuples during the vacuumcleanup scan that we're going to do anyway. Should save a few cycles (one calculation per page, not per tuple) as well as not having to depend on assumptions about heap and index being in step. I think this could probably be made to work for GIST too, but that code looks messy enough that I'm disinclined to try right now. Modified Files: -- pgsql/src/backend/access/nbtree: nbtree.c (r1.139 -> r1.140) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.139&r2=1.140) ---(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: Allow ALTER TABLE ...
[EMAIL PROTECTED] (Bruce Momjian) writes: > Log Message: > --- > Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME This patch appears seriously broken, in particular every routine I looked at contained incorrect locking assumptions. Nor do I care for using pg_depend for the purposes it's being used for here. regards, tom lane ---(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] pgfouine - www:
Log Message: --- Modified Files: -- www: index.html (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/www/index.html.diff?r1=1.9&r2=1.10) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] python - fe: Use the UnicodeType as the base for the String typing.
Log Message: --- Use the UnicodeType as the base for the String typing. Modified Files: -- fe/src: abstract.py (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/abstract.py.diff?r1=1.1.1.1&r2=1.2) ---(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: Use "x is [not] None" conditionals to help speed things
Log Message: --- Use "x is [not] None" conditionals to help speed things along. Modified Files: -- fe/src: tracenull.py (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Please find enclosed a patch that lets you use \c to connect
Log Message: --- Please find enclosed a patch that lets you use \c to connect (optionally) to a new host and port without exiting psql. This eliminates, IMHO, a surprise in that you can now connect to PostgreSQL on a differnt machine from the one where you started your session. This should help people who use psql as an administrative tool. David Fetter Modified Files: -- pgsql/doc/src/sgml/ref: psql-ref.sgml (r1.157 -> r1.158) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/psql-ref.sgml.diff?r1=1.157&r2=1.158) pgsql/src/bin/psql: command.c (r1.158 -> r1.159) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.158&r2=1.159) help.c (r1.107 -> r1.108) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/help.c.diff?r1=1.107&r2=1.108) ---(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: Restore previous psql behavior of not printing useless trailing
Log Message: --- Restore previous psql behavior of not printing useless trailing spaces after the data in the last column on a line. Modified Files: -- pgsql/src/bin/psql: print.c (r1.82 -> r1.83) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.c.diff?r1=1.82&r2=1.83) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Undo changes of trailing space in recently-committed expected
Log Message: --- Undo changes of trailing space in recently-committed expected files. This is mostly just over-compulsiveness on my part, but the exercise did reveal one real bug: errors.out has a space difference now where it should not. Modified Files: -- pgsql/src/test/regress/expected: inet.out (r1.21 -> r1.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/inet.out.diff?r1=1.21&r2=1.22) prepare.out (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/prepare.out.diff?r1=1.9&r2=1.10) ---(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: I've created a new shared catalog table pg_shdescription to store
Log Message: --- I've created a new shared catalog table pg_shdescription to store comments on cluster global objects like databases, tablespaces, and roles. It touches a lot of places, but not much in the way of big changes. The only design decision I made was to duplicate the query and manipulation functions rather than to try and have them handle both shared and local comments. I believe this is simpler for the code and not an issue for callers because they know what type of object they are dealing with. This has resulted in a shobj_description function analagous to obj_description and backend functions [Create/Delete]SharedComments mirroring the existing [Create/Delete]Comments functions. pg_shdescription.h goes into src/include/catalog/ Kris Jurka Modified Files: -- pgsql/doc/src/sgml: catalogs.sgml (r2.119 -> r2.120) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/catalogs.sgml.diff?r1=2.119&r2=2.120) func.sgml (r1.304 -> r1.305) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.304&r2=1.305) pgsql/doc/src/sgml/ref: comment.sgml (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/comment.sgml.diff?r1=1.29&r2=1.30) pgsql/src/backend/catalog: Makefile (r1.58 -> r1.59) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/Makefile.diff?r1=1.58&r2=1.59) genbki.sh (r1.37 -> r1.38) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/genbki.sh.diff?r1=1.37&r2=1.38) pgsql/src/backend/commands: comment.c (r1.85 -> r1.86) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/comment.c.diff?r1=1.85&r2=1.86) dbcommands.c (r1.175 -> r1.176) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c.diff?r1=1.175&r2=1.176) tablespace.c (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablespace.c.diff?r1=1.29&r2=1.30) user.c (r1.168 -> r1.169) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/user.c.diff?r1=1.168&r2=1.169) pgsql/src/backend/parser: gram.y (r2.527 -> r2.528) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.527&r2=2.528) pgsql/src/bin/initdb: initdb.c (r1.108 -> r1.109) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/initdb.c.diff?r1=1.108&r2=1.109) pgsql/src/bin/pg_dump: pg_dump.c (r1.427 -> r1.428) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c.diff?r1=1.427&r2=1.428) pg_dumpall.c (r1.69 -> r1.70) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dumpall.c.diff?r1=1.69&r2=1.70) pgsql/src/bin/psql: command.c (r1.159 -> r1.160) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.159&r2=1.160) describe.c (r1.130 -> r1.131) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/describe.c.diff?r1=1.130&r2=1.131) describe.h (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/describe.h.diff?r1=1.29&r2=1.30) tab-complete.c (r1.145 -> r1.146) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.145&r2=1.146) pgsql/src/include: postgres.h (r1.72 -> r1.73) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/postgres.h.diff?r1=1.72&r2=1.73) pgsql/src/include/catalog: catversion.h (r1.314 -> r1.315) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h.diff?r1=1.314&r2=1.315) indexing.h (r1.92 -> r1.93) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/indexing.h.diff?r1=1.92&r2=1.93) pg_database.h (r1.38 -> r1.39) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_database.h.diff?r1=1.38&r2=1.39) pg_proc.h (r1.396 -> r1.397) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h.diff?r1=1.396&r2=1.397) pgsql/src/include/commands: comment.h (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/commands/comment.h.diff?r1=1.16&r2=1.17) pgsql/src/test/regress/expected: sanity_check.out (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/sanity_check.out.diff?r1=1.29&r2=1.30) Added Files: --- pgsql/src/include/catalog: pg_shdescription.h (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_shdescription.h?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)-
[COMMITTERS] pgsql: New Directory
Update of /cvsroot/pgsql/contrib/pg_freespacemap In directory postgresql.org:/var/tmp/cvs-serv69212/pg_freespacemap Log Message: Directory /cvsroot/pgsql/contrib/pg_freespacemap added to the repository ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Fix more fallout from line-wrap patch, to wit, arbitrarily
Log Message: --- Fix more fallout from line-wrap patch, to wit, arbitrarily changing the API of PQdsplen without bothering to fix its callers. Although ReportSyntaxErrorPosition could probably do with more smarts about handling control characters, for the moment I'll just get it back to handling tabs consistently. Modified Files: -- pgsql/src/bin/psql: common.c (r1.111 -> r1.112) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/common.c.diff?r1=1.111&r2=1.112) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] python - fe: Clients can get PANIC ereports too.
Log Message: --- Clients can get PANIC ereports too. These are just as FATAL as 'FATAL'. Modified Files: -- fe/src: tracenull.py (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.diff?r1=1.4&r2=1.5) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Add contrib/pg_freespacemap to display free space map
Log Message: --- Add contrib/pg_freespacemap to display free space map information. Mark Kirkwood Modified Files: -- pgsql/contrib: Makefile (r1.61 -> r1.62) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/Makefile.diff?r1=1.61&r2=1.62) README (r1.82 -> r1.83) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/README.diff?r1=1.82&r2=1.83) pgsql/src/backend/storage/freespace: freespace.c (r1.50 -> r1.51) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/freespace/freespace.c.diff?r1=1.50&r2=1.51) pgsql/src/include/storage: freespace.h (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/freespace.h.diff?r1=1.18&r2=1.19) Added Files: --- pgsql/contrib/pg_freespacemap: Makefile (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/Makefile?rev=1.1&content-type=text/x-cvsweb-markup) README.pg_freespacemap (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/README.pg_freespacemap?rev=1.1&content-type=text/x-cvsweb-markup) pg_freespacemap.c (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/pg_freespacemap.c?rev=1.1&content-type=text/x-cvsweb-markup) pg_freespacemap.sql.in (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/pg_freespacemap.sql.in?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Done: > * -Add system view to show free space map contents
Log Message: --- Done: > * -Add system view to show free space map contents Modified Files: -- pgsql/doc: TODO (r1.1763 -> r1.1764) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1763&r2=1.1764) pgsql/doc/src/FAQ: TODO.html (r1.268 -> r1.269) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.268&r2=1.269) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Add psql option: -1 or --single-transaction Simon Riggs
Log Message: --- Add psql option: -1 or --single-transaction Simon Riggs Modified Files: -- pgsql/doc/src/sgml/ref: pg_restore.sgml (r1.56 -> r1.57) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_restore.sgml.diff?r1=1.56&r2=1.57) psql-ref.sgml (r1.158 -> r1.159) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/psql-ref.sgml.diff?r1=1.158&r2=1.159) pgsql/src/bin/pg_dump: pg_backup.h (r1.37 -> r1.38) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup.h.diff?r1=1.37&r2=1.38) pg_backup_archiver.c (r1.121 -> r1.122) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_archiver.c.diff?r1=1.121&r2=1.122) pg_restore.c (r1.73 -> r1.74) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_restore.c.diff?r1=1.73&r2=1.74) pgsql/src/bin/psql: command.c (r1.160 -> r1.161) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.160&r2=1.161) command.h (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.h.diff?r1=1.23&r2=1.24) help.c (r1.108 -> r1.109) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/help.c.diff?r1=1.108&r2=1.109) startup.c (r1.129 -> r1.130) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/startup.c.diff?r1=1.129&r2=1.130) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: As part of previous commit, add pg_restore option: -1 or
Log Message: --- As part of previous commit, add pg_restore option: -1 or --single-transaction Simon Riggs Modified Files: -- pgsql/src/bin/pg_dump: pg_restore.c (r1.74 -> r1.75) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_restore.c.diff?r1=1.74&r2=1.75) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Allow to_char() to print localized month and day names.
Log Message: --- Allow to_char() to print localized month and day names. Euler Taveira de Oliveira Modified Files: -- pgsql/doc/src/sgml: func.sgml (r1.305 -> r1.306) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.305&r2=1.306) pgsql/src/backend/utils/adt: formatting.c (r1.103 -> r1.104) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c.diff?r1=1.103&r2=1.104) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Done: > * -Allow to_char() to print localized month names
Log Message: --- Done: > * -Allow to_char() to print localized month names Modified Files: -- pgsql/doc: TODO (r1.1764 -> r1.1765) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1764&r2=1.1765) pgsql/doc/src/FAQ: TODO.html (r1.269 -> r1.270) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.269&r2=1.270) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Clean up plpgsql grammar to make sure that check_assignable() is
Log Message: --- Clean up plpgsql grammar to make sure that check_assignable() is applied consistently. This is mostly cosmetic right at the moment because check_assignable() does nothing for ROW or RECORD datums, but that might not always be so. This also syncs several different places that read INTO target lists. They're just enough different that it seems impractical to factor them into a single routine, but they surely should be the same as much as possible. Modified Files: -- pgsql/src/pl/plpgsql/src: gram.y (r1.82 -> r1.83) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.82&r2=1.83) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Use 0x01 for newlines in saved history.
Log Message: --- Use 0x01 for newlines in saved history. It was determined to be not used by multi-byte sequences, but futher invesetigation might prove this to be false. Modified Files: -- pgsql/src/bin/psql: input.c (r1.47 -> r1.48) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/input.c.diff?r1=1.47&r2=1.48) ---(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] python - fe: Fix dead-end detection.
Log Message: --- Fix dead-end detection. This resolves Proboscis' failure to detect the death of the remote end[1]. This can occur if the backend segfaults out; while this won't normally happen, if it does, Python's process use will go through the roof in an infinite loop. An earlier patch resolved the issue with seeing PANIC messages and treating them as fatal errors. Additionally, this resolves an issue where Python's CPU use goes through the roof when processing queries that take exceptional amounts of time to finish. This is due to transport's former use of non-blocking reads. This fixes the issue by requiring that at least one byte be read from the pipe. For sockets, this is done giving the MSG_WAITALL flag to recv. [1] http://pgfoundry.org/tracker/index.php?func=detail&aid=1000533&group_id=194&atid=442 Modified Files: -- fe/src: tracenull.py (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.diff?r1=1.5&r2=1.6) transport.py (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/transport.py.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: Allow PL/pgSQL FOR statement to return values to scalars as well
Log Message: --- Allow PL/pgSQL FOR statement to return values to scalars as well as records and row types. Pavel Stehule Modified Files: -- pgsql/doc/src/sgml: plpgsql.sgml (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plpgsql.sgml.diff?r1=1.84&r2=1.85) pgsql/src/pl/plpgsql/src: gram.y (r1.83 -> r1.84) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.83&r2=1.84) pgsql/src/test/regress/expected: plpgsql.out (r1.40 -> r1.41) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/plpgsql.out.diff?r1=1.40&r2=1.41) pgsql/src/test/regress/sql: plpgsql.sql (r1.34 -> r1.35) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/plpgsql.sql.diff?r1=1.34&r2=1.35) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Add MSVC support for utility commands and pg_dump.
Log Message: --- Add MSVC support for utility commands and pg_dump. Hiroshi Saito Modified Files: -- pgsql/doc/src/sgml: install-win32.sgml (r1.26 -> r1.27) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/install-win32.sgml.diff?r1=1.26&r2=1.27) pgsql/src: win32.mak (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/win32.mak.diff?r1=1.10&r2=1.11) pgsql/src/bin/pg_dump: pg_backup_archiver.c (r1.122 -> r1.123) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_archiver.c.diff?r1=1.122&r2=1.123) pg_backup_db.c (r1.68 -> r1.69) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_db.c.diff?r1=1.68&r2=1.69) pg_backup_null.c (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_null.c.diff?r1=1.16&r2=1.17) pg_backup_tar.c (r1.49 -> r1.50) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_tar.c.diff?r1=1.49&r2=1.50) pg_dump.c (r1.428 -> r1.429) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c.diff?r1=1.428&r2=1.429) pg_dumpall.c (r1.70 -> r1.71) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dumpall.c.diff?r1=1.70&r2=1.71) pg_restore.c (r1.75 -> r1.76) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_restore.c.diff?r1=1.75&r2=1.76) pgsql/src/include: pg_config.h.win32 (r1.25 -> r1.26) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config.h.win32.diff?r1=1.25&r2=1.26) Added Files: --- pgsql/src/bin/pg_dump: win32.mak (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/win32.mak?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] dbi-link - dbi-link: Makefile.PL opens the door to tests.
Log Message: --- Makefile.PL opens the door to tests. Kudos to Fred Moyer for coming up with this. Added Files: --- dbi-link: Makefile.PL (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/dbi-link/dbi-link/Makefile.PL?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Apply code-reviewed version of for-scalar-list patch: mostly,
Log Message: --- Apply code-reviewed version of for-scalar-list patch: mostly, fixing it to report reasonable errors in error cases. Modified Files: -- pgsql/doc/src/sgml: plpgsql.sgml (r1.85 -> r1.86) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plpgsql.sgml.diff?r1=1.85&r2=1.86) pgsql/src/pl/plpgsql/src: gram.y (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.84&r2=1.85) pgsql/src/test/regress/expected: plpgsql.out (r1.41 -> r1.42) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/plpgsql.out.diff?r1=1.41&r2=1.42) pgsql/src/test/regress/sql: plpgsql.sql (r1.35 -> r1.36) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/plpgsql.sql.diff?r1=1.35&r2=1.36) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Done: > * -Add COMMENT ON for all cluster global objects (roles,
Log Message: --- Done: > * -Add COMMENT ON for all cluster global objects (roles, databases Modified Files: -- pgsql/doc: TODO (r1.1765 -> r1.1766) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1765&r2=1.1766) pgsql/doc/src/FAQ: TODO.html (r1.270 -> r1.271) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.270&r2=1.271) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: List psql tab completion for various default keywords.
Log Message: --- List psql tab completion for various default keywords. Joachim Wieland Modified Files: -- pgsql/src/bin/psql: tab-complete.c (r1.146 -> r1.147) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.146&r2=1.147) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: When performing a parallel build (make -j N) with ./configure
Log Message: --- When performing a parallel build (make -j N) with ./configure --enable-depend it often tries to create the .deps directory twice and bails out when it already exists due to a race condition of if doesn't exist, then create. This patch prevents mkdir from returning an error. Kris Jurka Modified Files: -- pgsql/src: Makefile.global.in (r1.220 -> r1.221) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/Makefile.global.in.diff?r1=1.220&r2=1.221) ---(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
