[COMMITTERS] pgsql: Remove claim that this chapter discusses rules and triggers.

2009-09-11 Thread Peter Eisentraut
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.

[COMMITTERS] plproxy - plproxy: Fix potential buffer overflow when len(typname) > 32

2009-09-11 Thread User Mkz
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-b

[COMMITTERS] plproxy - plproxy: Fix argument value NULL check.

2009-09-11 Thread User Mkz
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: -

[COMMITTERS] pgsql: Increase the maximum value of extra_float_digits to 3, and have

2009-09-11 Thread Tom Lane
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 exact

[COMMITTERS] pgsql: Fix assertion failure when a SELECT DISTINCT ON expression is

2009-09-11 Thread Tom Lane
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 wa

[COMMITTERS] pgsql: Fix assertion failure when a SELECT DISTINCT ON expression is

2009-09-11 Thread Tom Lane
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 wa