[COMMITTERS] pgsql: Fix broken markup.
Log Message: --- Fix broken markup. Modified Files: -- pgsql/doc/src/sgml: pgbench.sgml (r1.11 -> r1.12) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/pgbench.sgml?r1=1.11&r2=1.12) -- 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: Support ORDER BY within aggregate function calls, at long last
Log Message: --- Support ORDER BY within aggregate function calls, at long last providing a non-kluge method for controlling the order in which values are fed to an aggregate function. At the same time eliminate the old implementation restriction that DISTINCT was only supported for single-argument aggregates. Possibly release-notable behavioral change: formerly, agg(DISTINCT x) dropped null values of x unconditionally. Now, it does so only if the agg transition function is strict; otherwise nulls are treated as DISTINCT normally would, ie, you get one copy. Andrew Gierth, reviewed by Hitoshi Harada Modified Files: -- pgsql/doc/src/sgml: func.sgml (r1.492 -> r1.493) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml?r1=1.492&r2=1.493) syntax.sgml (r1.138 -> r1.139) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/syntax.sgml?r1=1.138&r2=1.139) pgsql/src/backend/executor: nodeAgg.c (r1.169 -> r1.170) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeAgg.c?r1=1.169&r2=1.170) pgsql/src/backend/nodes: copyfuncs.c (r1.453 -> r1.454) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c?r1=1.453&r2=1.454) equalfuncs.c (r1.375 -> r1.376) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c?r1=1.375&r2=1.376) nodeFuncs.c (r1.43 -> r1.44) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/nodeFuncs.c?r1=1.43&r2=1.44) outfuncs.c (r1.374 -> r1.375) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c?r1=1.374&r2=1.375) readfuncs.c (r1.227 -> r1.228) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/readfuncs.c?r1=1.227&r2=1.228) pgsql/src/backend/optimizer/plan: planagg.c (r1.46 -> r1.47) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planagg.c?r1=1.46&r2=1.47) planner.c (r1.261 -> r1.262) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planner.c?r1=1.261&r2=1.262) pgsql/src/backend/optimizer/util: clauses.c (r1.280 -> r1.281) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c?r1=1.280&r2=1.281) pgsql/src/backend/parser: analyze.c (r1.396 -> r1.397) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c?r1=1.396&r2=1.397) gram.y (r2.696 -> r2.697) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y?r1=2.696&r2=2.697) parse_agg.c (r1.88 -> r1.89) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_agg.c?r1=1.88&r2=1.89) parse_clause.c (r1.193 -> r1.194) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_clause.c?r1=1.193&r2=1.194) parse_expr.c (r1.250 -> r1.251) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.250&r2=1.251) parse_func.c (r1.218 -> r1.219) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_func.c?r1=1.218&r2=1.219) parse_utilcmd.c (r2.31 -> r2.32) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_utilcmd.c?r1=2.31&r2=2.32) pgsql/src/backend/utils/adt: ruleutils.c (r1.316 -> r1.317) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ruleutils.c?r1=1.316&r2=1.317) pgsql/src/include/catalog: catversion.h (r1.557 -> r1.558) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h?r1=1.557&r2=1.558) pgsql/src/include/nodes: parsenodes.h (r1.418 -> r1.419) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h?r1=1.418&r2=1.419) primnodes.h (r1.151 -> r1.152) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/primnodes.h?r1=1.151&r2=1.152) pgsql/src/include/optimizer: clauses.h (r1.98 -> r1.99) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/clauses.h?r1=1.98&r2=1.99) pgsql/src/include/parser: parse_agg.h (r1.39 -> r1.40) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_agg.h?r1=1.39&r2=1.40) parse_clause.h (r1.56 -> r1.57) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_clause.h?r1=1.56&r2=1.57) parse_func.h (r1.66 -> r1.67) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_func.h?r1=1.66&r2=1.67) pgsql/src/test/regress/expected: aggregates.out (r1.19 -> r1.20) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/aggregates.out?r1=1.19&r2=1.20) create_aggregate.out (r1.6 -> r
Re: [COMMITTERS] pgsql: Add an EXPLAIN (BUFFERS) option to show buffer-usage statistics.
On Tue, 2009-12-15 at 04:57 +, Robert Haas wrote: > This patch also removes buffer-usage statistics from the track_counts > output, since this (or the global server statistics) is deemed to be a > better interface to this information. I hope anything being removed is documented, though I don't see that. Do you mean pg_statio_* tables no longer track heap_blocks* ? That is my understanding of what track_counts gives us. I think you mean log_*_stats, which is something else entirely. -- Simon Riggs www.2ndQuadrant.com -- 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 an EXPLAIN (BUFFERS) option to show buffer-usage statistics.
Simon Riggs escreveu: > On Tue, 2009-12-15 at 04:57 +, Robert Haas wrote: >> This patch also removes buffer-usage statistics from the track_counts >> output, since this (or the global server statistics) is deemed to be a >> better interface to this information. > > I hope anything being removed is documented, though I don't see that. > That functionality isn't documented AFAIR. That's why Tom suggested to rip it out. > Do you mean pg_statio_* tables no longer track heap_blocks* ? That is my > understanding of what track_counts gives us. I think you mean > log_*_stats, which is something else entirely. > That's it! -- Euler Taveira de Oliveira http://www.timbira.com/ -- 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 a hook to let loadable modules get control at ProcessUtility
Log Message: --- Add a hook to let loadable modules get control at ProcessUtility execution, and use it to extend contrib/pg_stat_statements to track utility commands. Itagaki Takahiro, reviewed by Euler Taveira de Oliveira. Modified Files: -- pgsql/contrib/pg_stat_statements: pg_stat_statements.c (r1.8 -> r1.9) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_stat_statements/pg_stat_statements.c?r1=1.8&r2=1.9) pgsql/doc/src/sgml: pgstatstatements.sgml (r1.4 -> r1.5) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/pgstatstatements.sgml?r1=1.4&r2=1.5) pgsql/src/backend/tcop: utility.c (r1.323 -> r1.324) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/utility.c?r1=1.323&r2=1.324) pgsql/src/include/tcop: utility.h (r1.37 -> r1.38) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/tcop/utility.h?r1=1.37&r2=1.38) -- 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 an EXPLAIN (BUFFERS) option to show buffer-usage statistics.
On Tue, Dec 15, 2009 at 1:32 PM, Simon Riggs wrote: > On Tue, 2009-12-15 at 04:57 +, Robert Haas wrote: >> This patch also removes buffer-usage statistics from the track_counts >> output, since this (or the global server statistics) is deemed to be a >> better interface to this information. > > I hope anything being removed is documented, though I don't see that. > Do you mean pg_statio_* tables no longer track heap_blocks* ? That is my > understanding of what track_counts gives us. I think you mean > log_*_stats, which is something else entirely. Oops. You're right, it's log_*_stats, rather than track_counts(). Unfortunately, the format of the log_*_stats output is not documented: we can't remove this from the list of things that log_*_stats is documented to print, because there is no such list. That might be worth correcting, but the lack of pre-existing documentation didn't seem like something this patch should try to fix. ...Robert -- 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: Avoid unnecessary copying of source string when generating a
Log Message: --- Avoid unnecessary copying of source string when generating a cloned TParser. For long source strings the copying results in O(N^2) behavior, and the multiplier can be significant if wide-char conversion is involved. Andres Freund, reviewed by Kevin Grittner. Modified Files: -- pgsql/src/backend/tsearch: wparser_def.c (r1.25 -> r1.26) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tsearch/wparser_def.c?r1=1.25&r2=1.26) -- 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: Python 3 support in PL/Python Behaves more or less unchanged
Log Message: --- Python 3 support in PL/Python Behaves more or less unchanged compared to Python 2, but the new language variant is called plpython3u. Documentation describing the naming scheme is included. Modified Files: -- pgsql: configure (r1.662 -> r1.663) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure?r1=1.662&r2=1.663) pgsql/config: python.m4 (r1.16 -> r1.17) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/config/python.m4?r1=1.16&r2=1.17) pgsql/doc/src/sgml: installation.sgml (r1.332 -> r1.333) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/installation.sgml?r1=1.332&r2=1.333) plpython.sgml (r1.41 -> r1.42) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plpython.sgml?r1=1.41&r2=1.42) pgsql/src: Makefile.global.in (r1.259 -> r1.260) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/Makefile.global.in?r1=1.259&r2=1.260) pgsql/src/include/catalog: catversion.h (r1.558 -> r1.559) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h?r1=1.558&r2=1.559) pg_pltemplate.h (r1.9 -> r1.10) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_pltemplate.h?r1=1.9&r2=1.10) pgsql/src/pl/plpython: Makefile (r1.34 -> r1.35) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/Makefile?r1=1.34&r2=1.35) plpython.c (r1.133 -> r1.134) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/plpython.c?r1=1.133&r2=1.134) pgsql/src/pl/plpython/expected: README (r1.4 -> r1.5) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/README?r1=1.4&r2=1.5) plpython_test.out (r1.13 -> r1.14) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/plpython_test.out?r1=1.13&r2=1.14) plpython_trigger.out (r1.6 -> r1.7) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/plpython_trigger.out?r1=1.6&r2=1.7) pgsql/src/pl/plpython/sql: plpython_test.sql (r1.9 -> r1.10) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/sql/plpython_test.sql?r1=1.9&r2=1.10) plpython_trigger.sql (r1.4 -> r1.5) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/sql/plpython_trigger.sql?r1=1.4&r2=1.5) Added Files: --- pgsql/src/pl/plpython/expected: plpython_types_3.out (r1.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/plpython_types_3.out?rev=1.1&content-type=text/x-cvsweb-markup) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
