[COMMITTERS] pgsql: Add a boolean GUC parameter "bonjour" to control whether a
Log Message: --- Add a boolean GUC parameter "bonjour" to control whether a Bonjour-enabled build actually attempts to advertise itself via Bonjour. Formerly it always did so, which meant that packagers had to decide for their users whether this behavior was wanted or not. The default is "off" to be on the safe side, though this represents a change in the default behavior of a Bonjour-enabled build. Per discussion. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.224 -> r1.225) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.224&r2=1.225) pgsql/src/backend/postmaster: postmaster.c (r1.595 -> r1.596) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.595&r2=1.596) pgsql/src/backend/utils/misc: guc.c (r1.515 -> r1.516) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.515&r2=1.516) postgresql.conf.sample (r1.264 -> r1.265) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample?r1=1.264&r2=1.265) pgsql/src/include/postmaster: postmaster.h (r1.20 -> r1.21) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/postmaster/postmaster.h?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] pgsql: Replace use of the long-deprecated Bonjour API
Log Message: --- Replace use of the long-deprecated Bonjour API DNSServiceRegistrationCreate with the not-so-deprecated DNSServiceRegister. This patch shouldn't change any user-visible behavior, it just gets rid of a deprecation warning in --with-bonjour builds. The new code will fail on OS X releases before 10.3, but it seems unlikely that anyone will want to run Postgres 8.5 on 10.2. Modified Files: -- pgsql: configure (r1.653 -> r1.654) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure?r1=1.653&r2=1.654) configure.in (r1.609 -> r1.610) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure.in?r1=1.609&r2=1.610) pgsql/src/backend/postmaster: postmaster.c (r1.594 -> r1.595) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.594&r2=1.595) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Remove any -arch switches given in ExtUtils::Embed's ldopts from
Log Message: --- Remove any -arch switches given in ExtUtils::Embed's ldopts from our perl_embed_ldflags setting. On OS X it seems that ExtUtils::Embed is trying to force a universal binary to be built, but you need to specify that a lot further upstream if you want Postgres built that way; the only result of including -arch in perl_embed_ldflags is some warnings at the plperl.so link step. Per my complaint and Jan Otto's suggestion. Modified Files: -- pgsql/config: perl.m4 (r1.4 -> r1.5) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/config/perl.m4?r1=1.4&r2=1.5) pgsql: configure (r1.654 -> r1.655) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure?r1=1.654&r2=1.655) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgstatsinfo - pg_statsinfo: - Add dblink_disconnect() to log cleanup
Log Message: --- - Add dblink_disconnect() to log cleanup function. Modified Files: -- pg_statsinfo/pg_statsinfo/stats_info: stats_info.sql.in (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgstatsinfo/pg_statsinfo/pg_statsinfo/stats_info/stats_info.sql.in?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: Fix bug with WITH RECURSIVE immediately inside WITH RECURSIVE.
Log Message: --- Fix bug with WITH RECURSIVE immediately inside WITH RECURSIVE. 99% of the code was already okay with this, but the hack that obtained the output column types of a recursive union in advance of doing real parse analysis of the recursive union forgot to handle the case where there was an inner WITH clause available to the non-recursive term. Best fix seems to be to refactor so that we don't need the "throwaway" parse analysis step at all. Instead, teach the transformSetOperationStmt code to set up the CTE's output column information after it's processed the non-recursive term normally. Per report from David Fetter. Modified Files: -- pgsql/src/backend/parser: analyze.c (r1.390 -> r1.391) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c?r1=1.390&r2=1.391) parse_clause.c (r1.191 -> r1.192) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_clause.c?r1=1.191&r2=1.192) parse_cte.c (r2.6 -> r2.7) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_cte.c?r1=2.6&r2=2.7) parse_expr.c (r1.242 -> r1.243) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.242&r2=1.243) pgsql/src/include/parser: analyze.h (r1.40 -> r1.41) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/analyze.h?r1=1.40&r2=1.41) parse_cte.h (r1.2 -> r1.3) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_cte.h?r1=1.2&r2=1.3) parse_node.h (r1.62 -> r1.63) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_node.h?r1=1.62&r2=1.63) pgsql/src/test/regress/expected: with.out (r1.11 -> r1.12) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/with.out?r1=1.11&r2=1.12) pgsql/src/test/regress/sql: with.sql (r1.10 -> r1.11) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/with.sql?r1=1.10&r2=1.11) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix bug with WITH RECURSIVE immediately inside WITH RECURSIVE.
Log Message: --- Fix bug with WITH RECURSIVE immediately inside WITH RECURSIVE. 99% of the code was already okay with this, but the hack that obtained the output column types of a recursive union in advance of doing real parse analysis of the recursive union forgot to handle the case where there was an inner WITH clause available to the non-recursive term. Best fix seems to be to refactor so that we don't need the "throwaway" parse analysis step at all. Instead, teach the transformSetOperationStmt code to set up the CTE's output column information after it's processed the non-recursive term normally. Per report from David Fetter. Tags: REL8_4_STABLE Modified Files: -- pgsql/src/backend/parser: analyze.c (r1.389.2.1 -> r1.389.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c?r1=1.389.2.1&r2=1.389.2.2) parse_clause.c (r1.189.2.1 -> r1.189.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_clause.c?r1=1.189.2.1&r2=1.189.2.2) parse_cte.c (r2.6 -> r2.6.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_cte.c?r1=2.6&r2=2.6.2.1) parse_expr.c (r1.241 -> r1.241.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.241&r2=1.241.2.1) pgsql/src/include/parser: analyze.h (r1.40 -> r1.40.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/analyze.h?r1=1.40&r2=1.40.2.1) parse_cte.h (r1.2 -> r1.2.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_cte.h?r1=1.2&r2=1.2.2.1) parse_node.h (r1.62 -> r1.62.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_node.h?r1=1.62&r2=1.62.2.1) pgsql/src/test/regress/expected: with.out (r1.10.2.1 -> r1.10.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/with.out?r1=1.10.2.1&r2=1.10.2.2) pgsql/src/test/regress/sql: with.sql (r1.9.2.1 -> r1.9.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/with.sql?r1=1.9.2.1&r2=1.9.2.2) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
