[COMMITTERS] pgsql: Allow binary-coercible types for cast function arguments and
Log Message: --- Allow binary-coercible types for cast function arguments and return types. Document return type of cast functions. Also change documentation to prefer the term "binary coercible" in its present sense instead of the previous term "binary compatible". Modified Files: -- pgsql/doc/src/sgml: catalogs.sgml (r2.166 -> r2.167) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/catalogs.sgml?r1=2.166&r2=2.167) typeconv.sgml (r1.53 -> r1.54) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/typeconv.sgml?r1=1.53&r2=1.54) pgsql/doc/src/sgml/ref: create_cast.sgml (r1.26 -> r1.27) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_cast.sgml?r1=1.26&r2=1.27) pgsql/src/backend/commands: functioncmds.c (r1.93 -> r1.94) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/functioncmds.c?r1=1.93&r2=1.94) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Add caching of query to GIN/GiST consistent function.
Log Message: --- Add caching of query to GIN/GiST consistent function. Per performance gripe from nomao.com Modified Files: -- pgsql/contrib/pg_trgm: trgm_gin.c (r1.4 -> r1.5) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_trgm/trgm_gin.c?r1=1.4&r2=1.5) trgm_gist.c (r1.14 -> r1.15) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_trgm/trgm_gist.c?r1=1.14&r2=1.15) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Allow binary-coercible types for cast function arguments and
[EMAIL PROTECTED] (Peter Eisentraut) writes: > Allow binary-coercible types for cast function arguments and return types. > Document return type of cast functions. > Also change documentation to prefer the term "binary coercible" in its > present sense instead of the previous term "binary compatible". Hmm, the error messages you added still use the phrase "binary compatible". [ click click, grep grep ] So does psql/describe.c. The only other hits I found were in comments, which likely aren't worth changing. regards, tom lane -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Add: > > * Add temporal versions of generate_series() > >
On Tue, 2008-03-11 at 17:42 +, Bruce Momjian wrote: > Log Message: > --- > Add: > > > > > * Add temporal versions of generate_series() > > > > http://archives.postgresql.org/pgsql-hackers/2007-04/msg01180.php > Committed 5 May 2008 -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix an oversight in the original implementation of
Log Message: --- Fix an oversight in the original implementation of performMultipleDeletions(): the alreadyDeleted list has to be passed down through deleteDependentObjects(), else objects that are deleted via auto/internal dependencies don't get reported back up to performMultipleDeletions(). Depending on the visitation order, this could cause the code to try to delete an already-deleted object, leading to strange errors in DROP OWNED (typically "cache lookup failed for relation N" or similar). Per bug #4289. Patch for back branches only. This code has recently been rewritten in HEAD, and doesn't have this particular bug anymore. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/backend/catalog: dependency.c (r1.69 -> r1.69.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/dependency.c?r1=1.69&r2=1.69.2.1) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix an oversight in the original implementation of
Log Message: --- Fix an oversight in the original implementation of performMultipleDeletions(): the alreadyDeleted list has to be passed down through deleteDependentObjects(), else objects that are deleted via auto/internal dependencies don't get reported back up to performMultipleDeletions(). Depending on the visitation order, this could cause the code to try to delete an already-deleted object, leading to strange errors in DROP OWNED (typically "cache lookup failed for relation N" or similar). Per bug #4289. Patch for back branches only. This code has recently been rewritten in HEAD, and doesn't have this particular bug anymore. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/backend/catalog: dependency.c (r1.60 -> r1.60.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/dependency.c?r1=1.60&r2=1.60.2.1) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Multi-column GIN indexes.
Log Message: --- Multi-column GIN indexes. Teodor Sigaev Modified Files: -- pgsql/doc/src/sgml: indices.sgml (r1.73 -> r1.74) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/indices.sgml?r1=1.73&r2=1.74) pgsql/doc/src/sgml/ref: create_index.sgml (r1.67 -> r1.68) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_index.sgml?r1=1.67&r2=1.68) pgsql/src/backend/access/gin: ginbulk.c (r1.12 -> r1.13) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginbulk.c?r1=1.12&r2=1.13) ginentrypage.c (r1.16 -> r1.17) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginentrypage.c?r1=1.16&r2=1.17) ginget.c (r1.17 -> r1.18) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginget.c?r1=1.17&r2=1.18) gininsert.c (r1.13 -> r1.14) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/gininsert.c?r1=1.13&r2=1.14) ginscan.c (r1.16 -> r1.17) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginscan.c?r1=1.16&r2=1.17) ginutil.c (r1.15 -> r1.16) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginutil.c?r1=1.15&r2=1.16) ginvacuum.c (r1.20 -> r1.21) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginvacuum.c?r1=1.20&r2=1.21) ginxlog.c (r1.14 -> r1.15) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginxlog.c?r1=1.14&r2=1.15) pgsql/src/include/access: gin.h (r1.22 -> r1.23) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.22&r2=1.23) pgsql/src/include/catalog: catversion.h (r1.465 -> r1.466) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h?r1=1.465&r2=1.466) pg_am.h (r1.56 -> r1.57) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_am.h?r1=1.56&r2=1.57) pgsql/src/test/regress/expected: create_index.out (r1.28 -> r1.29) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/create_index.out?r1=1.28&r2=1.29) pgsql/src/test/regress/sql: create_index.sql (r1.24 -> r1.25) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/create_index.sql?r1=1.24&r2=1.25) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Const-ify the arguments of str_tolower() and friends to suppress
Log Message: --- Const-ify the arguments of str_tolower() and friends to suppress compile warnings. Clean up various unneeded cruft that was left behind after creating those routines. Introduce some convenience functions str_tolower_z etc to eliminate tedious and error-prone double arguments in formatting.c. (Currently there seems no need to export the latter, but maybe reconsider this later.) Modified Files: -- pgsql/src/backend/utils/adt: formatting.c (r1.144 -> r1.145) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c?r1=1.144&r2=1.145) oracle_compat.c (r1.81 -> r1.82) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/oracle_compat.c?r1=1.81&r2=1.82) pgsql/src/include/utils: formatting.h (r1.19 -> r1.20) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/formatting.h?r1=1.19&r2=1.20) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Don't make --enable-cassert turn on RANDOMIZE_ALLOCATED_MEMORY
Log Message: --- Don't make --enable-cassert turn on RANDOMIZE_ALLOCATED_MEMORY automatically; it's just too dang expensive. Per recent discussion, but I just got my nose rubbed in it again while doing some performance checking. Modified Files: -- pgsql/src/include: pg_config_manual.h (r1.34 -> r1.35) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config_manual.h?r1=1.34&r2=1.35) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
