[COMMITTERS] pgsql: Continue to allow VACUUM to mark last block of index dirty
Continue to allow VACUUM to mark last block of index dirty even when there is no work to do. Further analysis required. Revert of patch c1458cc495ff800cd176a1c2e56d8b62680d9b71 Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/2d2841a56c8fa37a5dd5c6d33488ba6ca37116ff Modified Files -- src/backend/access/nbtree/nbtpage.c | 12 1 files changed, 4 insertions(+), 8 deletions(-) -- 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: Small markup and wording improvement
Small markup and wording improvement Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/024ea25ccd553aa0ecb41d626a1016470e25a9a0 Modified Files -- doc/src/sgml/information_schema.sgml |9 + 1 files changed, 5 insertions(+), 4 deletions(-) -- 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: Still more review for range-types patch.
Still more review for range-types patch. Per discussion, relax the range input/construction rules so that the only hard error is lower bound > upper bound. Cases where the lower bound is <= upper bound, but the range nonetheless normalizes to empty, are now permitted. Fix core dump in range_adjacent when bounds are infinite. Marginal cleanup of regression test cases, some more code commenting. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/766948beddef66dd89563f465919eca6e131861c Modified Files -- src/backend/utils/adt/rangetypes.c | 472 ++ src/backend/utils/adt/rangetypes_gist.c | 45 ++-- src/include/utils/rangetypes.h |5 + src/test/regress/expected/rangetypes.out | 309 src/test/regress/sql/rangetypes.sql | 97 --- 5 files changed, 556 insertions(+), 372 deletions(-) -- 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: Check for INSERT privileges in SELECT INTO / CREATE TABLE AS.
Check for INSERT privileges in SELECT INTO / CREATE TABLE AS. In the normal course of events, this matters only if ALTER DEFAULT PRIVILEGES has been used to revoke default INSERT permission. Whether or not the new behavior is more or less likely to be what the user wants when dealing only with the built-in privilege facilities is arguable, but it's clearly better when using a loadable module such as sepgsql that may use the hook in ExecCheckRTPerms to enforce additional permissions checks. KaiGai Kohei, reviewed by Albe Laurenz Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f1b4aa2a84732255bd8a34fc9c7994a04409b77a Modified Files -- src/backend/executor/execMain.c | 17 src/test/regress/expected/select_into.out | 39 + src/test/regress/sql/select_into.sql | 37 +++ 3 files changed, 93 insertions(+), 0 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] psqlodbc - psqlodbc: Clear col_info(columns info) cache ehen DROP/ALTER
Log Message: --- Clear col_info(columns info) cache ehen DROP/ALTER TABLE is called so that later SQLDescribeCol() etc work properly. Modified Files: -- psqlodbc: connection.c (r1.195 -> r1.196) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.c?r1=1.195&r2=1.196) -- 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: Improve implementation of range-contains-element tests.
Improve implementation of range-contains-element tests. Implement these tests directly instead of constructing a singleton range and then applying range-contains. This saves a range serialize/deserialize cycle as well as a couple of redundant bound-comparison steps, and adds very little code on net. Remove elem_contained_by_range from the GiST opclass: it doesn't belong there because there is no way to use it in an index clause (where the indexed column would have to be on the left). Its commutator is in the opclass, and that's what counts. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cddc819e45010492da00164d225a749661f43aef Modified Files -- src/backend/utils/adt/rangetypes.c | 65 ++- src/backend/utils/adt/rangetypes_gist.c | 105 -- src/include/catalog/catversion.h |2 +- src/include/catalog/pg_amop.h|1 - src/test/regress/expected/opr_sanity.out |3 +- 5 files changed, 92 insertions(+), 84 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] psqlodbc - psqlodbc: add the change history.
Log Message: --- add the change history. Modified Files: -- psqlodbc/docs: release.html (r1.79 -> r1.80) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/docs/release.html?r1=1.79&r2=1.80) -- 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: Remove zero- and one-argument range constructor functions.
Remove zero- and one-argument range constructor functions. Per discussion, the zero-argument forms aren't really worth the catalog space (just write 'empty' instead). The one-argument forms have some use, but they also have a serious problem with looking too much like functional cast notation; to the point where in many real use-cases, the parser would misinterpret what was wanted. Committing this as a separate patch, with the thought that we might want to revert part or all of it if we can think of some way around the cast ambiguity. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/df73584431e7edb1dd76578777bd0fcc17b916a1 Modified Files -- doc/src/sgml/rangetypes.sgml | 20 +++--- src/backend/commands/typecmds.c |6 +-- src/backend/utils/adt/rangetypes.c | 58 -- src/include/catalog/catversion.h |2 +- src/include/catalog/pg_proc.h| 24 src/include/utils/rangetypes.h |3 -- src/test/regress/expected/rangetypes.out | 16 src/test/regress/sql/rangetypes.sql | 14 8 files changed, 24 insertions(+), 119 deletions(-) -- 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: Remove user-selectable ANALYZE option for range types.
Remove user-selectable ANALYZE option for range types. It's not clear that a per-datatype typanalyze function would be any more useful than a generic typanalyze for ranges. What *is* clear is that letting unprivileged users select typanalyze functions is a crash risk or worse. So remove the option from CREATE TYPE AS RANGE, and instead put in a generic typanalyze function for ranges. The generic function does nothing as yet, but hopefully we'll improve that before 9.2 release. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/74c1723fc8dca2d70576ef2f0a66f4a7c99c173a Modified Files -- doc/src/sgml/ref/create_type.sgml |7 --- src/backend/commands/typecmds.c| 18 +- src/backend/utils/adt/rangetypes.c | 17 + src/bin/pg_dump/pg_dump.c | 14 +- src/include/catalog/catversion.h |2 +- src/include/catalog/pg_proc.h |3 +++ src/include/catalog/pg_type.h | 12 ++-- src/include/utils/rangetypes.h |3 +++ 8 files changed, 36 insertions(+), 40 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
