[COMMITTERS] pgsql: Add mention of why malloc() has to be used in snprintf.c.
Log Message: --- Add mention of why malloc() has to be used in snprintf.c. Modified Files: -- pgsql/src/port: snprintf.c (r1.25 -> r1.26) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/snprintf.c.diff?r1=1.25&r2=1.26) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgaccess - pgaccess: added a third param to showError for parent window
Log Message: --- added a third param to showError for parent window name Modified Files: -- pgaccess/main: util.tcl (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgaccess/pgaccess/main/util.tcl.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Remove unnecessary calls of FlushRelationBuffers: there is no
Log Message: --- Remove unnecessary calls of FlushRelationBuffers: there is no need to write out data that we are about to tell the filesystem to drop. smgr_internal_unlink already had a DropRelFileNodeBuffers call to get rid of dead buffers without a write after it's no longer possible to roll back the deleting transaction. Adding a similar call in smgrtruncate simplifies callers and makes the overall division of labor clearer. This patch removes the former behavior that VACUUM would write all dirty buffers of a relation unconditionally. Modified Files: -- pgsql/src/backend/access/nbtree: nbtree.c (r1.124 -> r1.125) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.124&r2=1.125) pgsql/src/backend/catalog: heap.c (r1.280 -> r1.281) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/heap.c.diff?r1=1.280&r2=1.281) index.c (r1.247 -> r1.248) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/index.c.diff?r1=1.247&r2=1.248) pgsql/src/backend/commands: cluster.c (r1.132 -> r1.133) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/cluster.c.diff?r1=1.132&r2=1.133) tablecmds.c (r1.147 -> r1.148) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablecmds.c.diff?r1=1.147&r2=1.148) vacuum.c (r1.304 -> r1.305) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.304&r2=1.305) vacuumlazy.c (r1.50 -> r1.51) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.50&r2=1.51) pgsql/src/backend/storage/buffer: bufmgr.c (r1.187 -> r1.188) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/buffer/bufmgr.c.diff?r1=1.187&r2=1.188) pgsql/src/backend/storage/smgr: smgr.c (r1.85 -> r1.86) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/smgr/smgr.c.diff?r1=1.85&r2=1.86) pgsql/src/include/storage: bufmgr.h (r1.92 -> r1.93) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/bufmgr.h.diff?r1=1.92&r2=1.93) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: On Windows, use QueryPerformanceCounter instead of gettimeofday
Log Message: --- On Windows, use QueryPerformanceCounter instead of gettimeofday for EXPLAIN ANALYZE instrumentation. Magnus Hagander Modified Files: -- pgsql/src/backend/commands: explain.c (r1.129 -> r1.130) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/explain.c.diff?r1=1.129&r2=1.130) pgsql/src/backend/executor: instrument.c (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/instrument.c.diff?r1=1.9&r2=1.10) pgsql/src/include/executor: instrument.h (r1.8 -> r1.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/executor/instrument.h.diff?r1=1.8&r2=1.9) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Change the return value of HeapTupleSatisfiesUpdate() to be an
Log Message: --- Change the return value of HeapTupleSatisfiesUpdate() to be an enum, rather than an integer, and fix the associated fallout. From Alvaro Herrera. Modified Files: -- pgsql/src/backend/access/heap: heapam.c (r1.183 -> r1.184) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/heapam.c.diff?r1=1.183&r2=1.184) pgsql/src/backend/commands: async.c (r1.119 -> r1.120) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/async.c.diff?r1=1.119&r2=1.120) trigger.c (r1.177 -> r1.178) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/trigger.c.diff?r1=1.177&r2=1.178) pgsql/src/backend/executor: execMain.c (r1.242 -> r1.243) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execMain.c.diff?r1=1.242&r2=1.243) pgsql/src/backend/utils/time: tqual.c (r1.85 -> r1.86) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c.diff?r1=1.85&r2=1.86) pgsql/src/include/access: heapam.h (r1.96 -> r1.97) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/heapam.h.diff?r1=1.96&r2=1.97) pgsql/src/include/utils: tqual.h (r1.55 -> r1.56) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/tqual.h.diff?r1=1.55&r2=1.56) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] docbot - docbot: config module added
Log Message: --- config module added Modified Files: -- docbot: docbot.pl (r1.24 -> r1.25) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/docbot/docbot/docbot.pl.diff?r1=1.24&r2=1.25) Added Files: --- docbot: config.pm (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/docbot/docbot/config.pm?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql: Convert index-related tuple handling routines from char 'n'/' '
Log Message: --- Convert index-related tuple handling routines from char 'n'/' ' to bool convention for isnull flags. Also, remove the useless InsertIndexResult return struct from index AM aminsert calls --- there is no reason for the caller to know where in the index the tuple was inserted, and we were wasting a palloc cycle per insert to deliver this uninteresting value (plus nontrivial complexity in some AMs). I forced initdb because of the change in the signature of the aminsert routines, even though nothing really looks at those pg_proc entries... Modified Files: -- pgsql/doc/src/sgml: indexam.sgml (r2.1 -> r2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/indexam.sgml.diff?r1=2.1&r2=2.2) pgsql/src/backend/access/common: heaptuple.c (r1.98 -> r1.99) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/common/heaptuple.c.diff?r1=1.98&r2=1.99) indextuple.c (r1.72 -> r1.73) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/common/indextuple.c.diff?r1=1.72&r2=1.73) pgsql/src/backend/access/gist: gist.c (r1.112 -> r1.113) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gist.c.diff?r1=1.112&r2=1.113) pgsql/src/backend/access/hash: hash.c (r1.76 -> r1.77) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hash.c.diff?r1=1.76&r2=1.77) hashinsert.c (r1.35 -> r1.36) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashinsert.c.diff?r1=1.35&r2=1.36) pgsql/src/backend/access/heap: tuptoaster.c (r1.48 -> r1.49) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/tuptoaster.c.diff?r1=1.48&r2=1.49) pgsql/src/backend/access/index: indexam.c (r1.77 -> r1.78) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/index/indexam.c.diff?r1=1.77&r2=1.78) pgsql/src/backend/access/nbtree: nbtinsert.c (r1.119 -> r1.120) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtinsert.c.diff?r1=1.119&r2=1.120) nbtree.c (r1.125 -> r1.126) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.125&r2=1.126) pgsql/src/backend/access/rtree: rtree.c (r1.87 -> r1.88) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/rtree/rtree.c.diff?r1=1.87&r2=1.88) pgsql/src/backend/catalog: index.c (r1.248 -> r1.249) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/index.c.diff?r1=1.248&r2=1.249) indexing.c (r1.108 -> r1.109) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/indexing.c.diff?r1=1.108&r2=1.109) pgsql/src/backend/commands: analyze.c (r1.83 -> r1.84) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/analyze.c.diff?r1=1.83&r2=1.84) pgsql/src/backend/executor: execUtils.c (r1.118 -> r1.119) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execUtils.c.diff?r1=1.118&r2=1.119) pgsql/src/include/access: genam.h (r1.47 -> r1.48) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/genam.h.diff?r1=1.47&r2=1.48) hash.h (r1.59 -> r1.60) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/hash.h.diff?r1=1.59&r2=1.60) heapam.h (r1.97 -> r1.98) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/heapam.h.diff?r1=1.97&r2=1.98) itup.h (r1.41 -> r1.42) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/itup.h.diff?r1=1.41&r2=1.42) nbtree.h (r1.83 -> r1.84) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/nbtree.h.diff?r1=1.83&r2=1.84) tuptoaster.h (r1.21 -> r1.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/tuptoaster.h.diff?r1=1.21&r2=1.22) pgsql/src/include/catalog: catversion.h (r1.258 -> r1.259) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h.diff?r1=1.258&r2=1.259) index.h (r1.60 -> r1.61) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/index.h.diff?r1=1.60&r2=1.61) pg_proc.h (r1.352 -> r1.353) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h.diff?r1=1.352&r2=1.353) ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql: * construct "struct {} list [] = {}" confuses pgindent - split
Log Message:
---
* construct "struct {} list [] = {}" confuses pgindent - split those.
It was a bad style to begin with, and now several loops can be clearer.
* pgcrypto.c: Fix function comments
* crypt-gensalt.c, crypt-blowfish.c: stop messing with errno
* openssl.c: use px_free instead pfree
* px.h: make redefining px_alloc/px_realloc/px_free easier
Marko Kreen
Modified Files:
--
pgsql/contrib/pgcrypto:
crypt-blowfish.c (r1.7 -> r1.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/crypt-blowfish.c.diff?r1=1.7&r2=1.8)
crypt-gensalt.c (r1.4 -> r1.5)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/crypt-gensalt.c.diff?r1=1.4&r2=1.5)
internal.c (r1.14 -> r1.15)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/internal.c.diff?r1=1.14&r2=1.15)
openssl.c (r1.14 -> r1.15)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/openssl.c.diff?r1=1.14&r2=1.15)
pgcrypto.c (r1.16 -> r1.17)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/pgcrypto.c.diff?r1=1.16&r2=1.17)
px-crypt.c (r1.8 -> r1.9)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px-crypt.c.diff?r1=1.8&r2=1.9)
px.h (r1.9 -> r1.10)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px.h.diff?r1=1.9&r2=1.10)
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: pgcrypto update: * Use error codes instead of -1 * px_strerror
Log Message: --- pgcrypto update: * Use error codes instead of -1 * px_strerror for new error codes * calling convention change for px_gen_salt - return error code * use px_strerror in pgcrypto.c Marko Kreen Modified Files: -- pgsql/contrib/pgcrypto: internal.c (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/internal.c.diff?r1=1.15&r2=1.16) openssl.c (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/openssl.c.diff?r1=1.15&r2=1.16) pgcrypto.c (r1.17 -> r1.18) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/pgcrypto.c.diff?r1=1.17&r2=1.18) px-crypt.c (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px-crypt.c.diff?r1=1.9&r2=1.10) px-crypt.h (r1.6 -> r1.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px-crypt.h.diff?r1=1.6&r2=1.7) px-hmac.c (r1.5 -> r1.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px-hmac.c.diff?r1=1.5&r2=1.6) px.c (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px.c.diff?r1=1.9&r2=1.10) px.h (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px.h.diff?r1=1.10&r2=1.11) random.c (r1.8 -> r1.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/random.c.diff?r1=1.8&r2=1.9) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: pgcrypto update: Reserve px_get_random_bytes() for strong
Log Message: --- pgcrypto update: Reserve px_get_random_bytes() for strong randomness, add new function px_get_pseudo_random_bytes() for weak randomness and use it in gen_salt(). On openssl case, use RAND_pseudo_bytes() for px_get_pseudo_random_bytes(). Final result is that is user has not configured random souce but kept the 'silly' one, gen_salt() keeps working, but pgp_encrypt() will throw error. Marko Kreen Modified Files: -- pgsql/contrib/pgcrypto: px-crypt.c (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px-crypt.c.diff?r1=1.10&r2=1.11) px.c (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px.c.diff?r1=1.10&r2=1.11) px.h (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/px.h.diff?r1=1.11&r2=1.12) random.c (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/random.c.diff?r1=1.9&r2=1.10) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Remove support for libmhash/libmcrypt.
Log Message: --- Remove support for libmhash/libmcrypt. libmcrypt seems to dead, maintainer address bounces, and cast-128 fails on 2 of the 3 test vectors from RFC2144. So I see no reason to keep around stuff I don't trust anymore. Support for several crypto libraries is probably only confusing to users, although it was good for initial developing - it helped to find hidden assumptions and forced me to create regression tests for all functionality. Marko Kreen Modified Files: -- pgsql/contrib/pgcrypto: Makefile (r1.12 -> r1.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/Makefile.diff?r1=1.12&r2=1.13) README.pgcrypto (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/README.pgcrypto.diff?r1=1.7&r2=1.8) Removed Files: - pgsql/contrib/pgcrypto: mhash.c (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/mhash.c) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: pgcrypto update: * test error handling * add tests for des,
Log Message: --- pgcrypto update: * test error handling * add tests for des, 3des, cast5 * add some tests to blowfish, rijndael * Makefile: ability to specify different tests for different crypto libraries, so we can skip des, 3des and cast5 for builtin. Marko Kreen Modified Files: -- pgsql/contrib/pgcrypto: Makefile (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/Makefile.diff?r1=1.13&r2=1.14) pgsql/contrib/pgcrypto/expected: blowfish.out (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/blowfish.out.diff?r1=1.3&r2=1.4) init.out (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/init.out.diff?r1=1.2&r2=1.3) rijndael.out (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/rijndael.out.diff?r1=1.3&r2=1.4) pgsql/contrib/pgcrypto/sql: blowfish.sql (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sql/blowfish.sql.diff?r1=1.3&r2=1.4) init.sql (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sql/init.sql.diff?r1=1.3&r2=1.4) rijndael.sql (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sql/rijndael.sql.diff?r1=1.3&r2=1.4) Added Files: --- pgsql/contrib/pgcrypto/expected: 3des.out (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/3des.out?rev=1.1&content-type=text/x-cvsweb-markup) cast5.out (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/cast5.out?rev=1.1&content-type=text/x-cvsweb-markup) des.out (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/des.out?rev=1.1&content-type=text/x-cvsweb-markup) pgsql/contrib/pgcrypto/sql: 3des.sql (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sql/3des.sql?rev=1.1&content-type=text/x-cvsweb-markup) cast5.sql (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sql/cast5.sql?rev=1.1&content-type=text/x-cvsweb-markup) des.sql (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sql/des.sql?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: pgcrypto update: * openssl.c: Add 3des and AES support *
Log Message: --- pgcrypto update: * openssl.c: Add 3des and AES support * README.pgcrypto: list only supported ciphers for openssl OpenSSL has pre-processor symbol OPENSSL_NO_AES, which isn't that helpful for detecting if it _does_ exist. Thus the hack with AES_ENCRYPT. Marko Kreen Modified Files: -- pgsql/contrib/pgcrypto: README.pgcrypto (r1.8 -> r1.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/README.pgcrypto.diff?r1=1.8&r2=1.9) openssl.c (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/openssl.c.diff?r1=1.16&r2=1.17) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
