[COMMITTERS] pgsql: Remove claim that this chapter discusses rules and triggers.
Log Message: --- Remove claim that this chapter discusses rules and triggers. per Bruno Guimarães Carneiro Modified Files: -- pgsql/doc/src/sgml: dml.sgml (r1.20 -> r1.21) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/dml.sgml?r1=1.20&r2=1.21) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] plproxy - plproxy: Fix potential buffer overflow when len(typname) > 32
Log Message: --- Fix potential buffer overflow when len(typname) > 32 The fixed size buffer tmp[32] was not updated when type casting was added. Reported by Ian Sollars Modified Files: -- plproxy/src: query.c (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/src/query.c?r1=1.7&r2=1.8) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] plproxy - plproxy: Fix argument value NULL check.
Log Message: --- Fix argument value NULL check. Incoming NULL value could cause crash in function containing SELECT with different argument order. Due to thinko, NULL check was done with query arg index, instead of function arg index. Reported by João Matos Modified Files: -- plproxy/src: execute.c (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/src/execute.c?r1=1.16&r2=1.17) plproxy/sql: plproxy_select.sql (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/sql/plproxy_select.sql?r1=1.3&r2=1.4) plproxy/expected: plproxy_select.out (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/expected/plproxy_select.out?r1=1.4&r2=1.5) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Increase the maximum value of extra_float_digits to 3, and have
Log Message: --- Increase the maximum value of extra_float_digits to 3, and have pg_dump use that value when the backend is new enough to allow it. This responds to bug report from Keh-Cheng Chu pointing out that although 2 extra digits should be sufficient to dump and restore float8 exactly, it is possible to need 3 extra digits for float4 values. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.226 -> r1.227) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.226&r2=1.227) pgsql/src/backend/utils/adt: float.c (r1.162 -> r1.163) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/float.c?r1=1.162&r2=1.163) geo_ops.c (r1.104 -> r1.105) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/geo_ops.c?r1=1.104&r2=1.105) pgsql/src/backend/utils/misc: guc.c (r1.516 -> r1.517) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.516&r2=1.517) postgresql.conf.sample (r1.265 -> r1.266) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample?r1=1.265&r2=1.266) pgsql/src/bin/pg_dump: pg_dump.c (r1.546 -> r1.547) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c?r1=1.546&r2=1.547) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix assertion failure when a SELECT DISTINCT ON expression is
Log Message: --- Fix assertion failure when a SELECT DISTINCT ON expression is volatile. In this case we generate two PathKey references to the expression (one for DISTINCT and one for ORDER BY) and they really need to refer to the same EquivalenceClass. However get_eclass_for_sort_expr was being overly paranoid and creating two different EC's. Correct behavior is to use the SortGroupRef index to decide whether two references to volatile expressions that are equal() (ie textually equivalent) should be considered the same. Backpatch to 8.4. Possibly this should be changed in 8.3 as well, but I'll refrain in the absence of evidence of a visible failure in that branch. Per bug #5049. Tags: REL8_4_STABLE Modified Files: -- pgsql/src/backend/optimizer/path: equivclass.c (r1.19 -> r1.19.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/equivclass.c?r1=1.19&r2=1.19.2.1) pathkeys.c (r1.97.2.1 -> r1.97.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c?r1=1.97.2.1&r2=1.97.2.2) pgsql/src/test/regress/expected: select_distinct_on.out (r1.5 -> r1.5.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/select_distinct_on.out?r1=1.5&r2=1.5.2.1) pgsql/src/test/regress/sql: select_distinct_on.sql (r1.4 -> r1.4.24.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/select_distinct_on.sql?r1=1.4&r2=1.4.24.1) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix assertion failure when a SELECT DISTINCT ON expression is
Log Message: --- Fix assertion failure when a SELECT DISTINCT ON expression is volatile. In this case we generate two PathKey references to the expression (one for DISTINCT and one for ORDER BY) and they really need to refer to the same EquivalenceClass. However get_eclass_for_sort_expr was being overly paranoid and creating two different EC's. Correct behavior is to use the SortGroupRef index to decide whether two references to volatile expressions that are equal() (ie textually equivalent) should be considered the same. Backpatch to 8.4. Possibly this should be changed in 8.3 as well, but I'll refrain in the absence of evidence of a visible failure in that branch. Per bug #5049. Modified Files: -- pgsql/src/backend/optimizer/path: equivclass.c (r1.19 -> r1.20) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/equivclass.c?r1=1.19&r2=1.20) pathkeys.c (r1.98 -> r1.99) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c?r1=1.98&r2=1.99) pgsql/src/test/regress/expected: select_distinct_on.out (r1.5 -> r1.6) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/select_distinct_on.out?r1=1.5&r2=1.6) pgsql/src/test/regress/sql: select_distinct_on.sql (r1.4 -> r1.5) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/select_distinct_on.sql?r1=1.4&r2=1.5) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
