[COMMITTERS] pgsql: Fix MSVC builds broken by xsubpp change

2011-11-26 Thread Andrew Dunstan
Fix MSVC builds broken by xsubpp change Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/bcba9acf0d56d3fd5aa37c4ba6b24b6084032e58 Modified Files -- src/tools/msvc/Mkvcbuild.pm |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) -- Sent vi

[COMMITTERS] pgsql: Fix MSVC builds broken by xsubpp change

2011-11-26 Thread Andrew Dunstan
Fix MSVC builds broken by xsubpp change Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4a9018135a37203e176a561913453b38788ac7da Modified Files -- src/tools/msvc/Mkvcbuild.pm |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) -- Sent via pgsql

[COMMITTERS] pgsql: Move pg_dump memory routines into pg_dumpmem.c/h and restore com

2011-11-26 Thread Bruce Momjian
Move pg_dump memory routines into pg_dumpmem.c/h and restore common.c with its original functions. The previous function migration would cause too many difficulties in back-patching. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9a7d49d1fba666c8bfb9df0065545e85d54d

[COMMITTERS] pgsql: Use the right interpreter for encoding test.

2011-11-26 Thread Andrew Dunstan
Use the right interpreter for encoding test. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9f42e5b3ecd91e0f3da278bec5d8255c1e913e62 Modified Files -- src/pl/plperl/expected/plperl.out |2 +- src/pl/plperl/sql/plperl.sql |2 +- 2 files

[COMMITTERS] pgsql: Use the right interpreter for encoding test.

2011-11-26 Thread Andrew Dunstan
Use the right interpreter for encoding test. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/efb0423cc7c6e46c22816e2acc48e8f827e341ed Modified Files -- src/pl/plperl/expected/plperl.out |2 +- src/pl/plperl/sql/plperl.sql |2 +- 2 files changed

Re: [COMMITTERS] pgsql: Ensure plperl strings are always correctly UTF8 encoded.

2011-11-26 Thread Andrew Dunstan
On 11/26/2011 06:07 PM, Tom Lane wrote: Andrew Dunstan writes: Ensure plperl strings are always correctly UTF8 encoded. Amit Khandekar and Alex Hunsaker. This patch broke the buildfarm members that don't support multiple Perl interpreters, apparently because of an entirely random decision ab

Re: [COMMITTERS] pgsql: Ensure plperl strings are always correctly UTF8 encoded.

2011-11-26 Thread Tom Lane
Andrew Dunstan writes: > Ensure plperl strings are always correctly UTF8 encoded. > Amit Khandekar and Alex Hunsaker. This patch broke the buildfarm members that don't support multiple Perl interpreters, apparently because of an entirely random decision about which plperl variant to test where.

[COMMITTERS] pgfiledump - pg_filedump: Update for Postgres 9.1; add knowledge of some

2011-11-26 Thread User Tgl
Log Message: --- Update for Postgres 9.1; add knowledge of some more flag bits; improve Makefile to be able to build a release tarball. Modified Files: -- pg_filedump: Makefile (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfiledump/pg_filedu

[COMMITTERS] pgsql: Use the preferred version of xsubpp, not necessarily the one tha

2011-11-26 Thread Andrew Dunstan
Use the preferred version of xsubpp, not necessarily the one that came with the distro version of perl. David Wheeler and Alex Hunsaker. Backpatch to 9.1 where it applies cleanly. A simple workaround is available for earlier branches, and further effort doesn't seem warranted. Branch -- REL

[COMMITTERS] pgsql: Use the preferred version of xsubpp, not necessarily the one tha

2011-11-26 Thread Andrew Dunstan
Use the preferred version of xsubpp, not necessarily the one that came with the distro version of perl. David Wheeler and Alex Hunsaker. Backpatch to 9.1 where it applies cleanly. A simple workaround is available for earlier branches, and further effort doesn't seem warranted. Branch -- mas

[COMMITTERS] pgsql: Make GiST index searches smarter about queries against empty ran

2011-11-26 Thread Tom Lane
Make GiST index searches smarter about queries against empty ranges. In the cases where the result of the called proc is negated, we should explicitly test both inputs for empty, to ensure we'll never return "true" for an unsatisfiable query. In other cases we can rely on the called proc to say t

[COMMITTERS] pgsql: Fix overly-aggressive and inconsistent quoting in OS X start scr

2011-11-26 Thread Tom Lane
Fix overly-aggressive and inconsistent quoting in OS X start script. Sidar Lopez, per bug #6310, with some additional improvements by me. Back-patch to 9.0, where the issue was introduced. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/19d88c9f82b9a2b0e8497ec

[COMMITTERS] pgsql: Fix overly-aggressive and inconsistent quoting in OS X start scr

2011-11-26 Thread Tom Lane
Fix overly-aggressive and inconsistent quoting in OS X start script. Sidar Lopez, per bug #6310, with some additional improvements by me. Back-patch to 9.0, where the issue was introduced. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/87b0dcf490ffe2930940488

[COMMITTERS] pgsql: Fix overly-aggressive and inconsistent quoting in OS X start scr

2011-11-26 Thread Tom Lane
Fix overly-aggressive and inconsistent quoting in OS X start script. Sidar Lopez, per bug #6310, with some additional improvements by me. Back-patch to 9.0, where the issue was introduced. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6c8768c3861d6690656b74676c44ff

[COMMITTERS] pgsql: Ensure plperl strings are always correctly UTF8 encoded.

2011-11-26 Thread Andrew Dunstan
Ensure plperl strings are always correctly UTF8 encoded. Amit Khandekar and Alex Hunsaker. Backpatched to 9.1 where the problem first occurred. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/e75d41f0c3e69fefe24a98514b897716d60a83dd Modified Files --

[COMMITTERS] pgsql: Ensure plperl strings are always correctly UTF8 encoded.

2011-11-26 Thread Andrew Dunstan
Ensure plperl strings are always correctly UTF8 encoded. Amit Khandekar and Alex Hunsaker. Backpatched to 9.1 where the problem first occurred. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4cdb41b54e432ee75e3c61e990b735b15fa66e81 Modified Files -- sr

Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

2011-11-26 Thread Andrew Dunstan
On 11/26/2011 09:18 AM, Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian writes: Modify pg_dump to use error-free memory allocation macros. This avoids ignoring errors and call-site error checking. This appears to have broken the MSVC build. More generally, I'd like to Doesn't the MSVC

Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

2011-11-26 Thread Bruce Momjian
Bruce Momjian wrote: > Tom Lane wrote: > > Bruce Momjian writes: > > > Modify pg_dump to use error-free memory allocation macros. This avoids > > > ignoring errors and call-site error checking. > > > > This appears to have broken the MSVC build. More generally, I'd like to > > Doesn't the MSVC

Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

2011-11-26 Thread Bruce Momjian
Andrew Dunstan wrote: > > > On 11/26/2011 09:11 AM, Bruce Momjian wrote: > > \Andrew Dunstan wrote: > >> > >> On 11/26/2011 02:13 AM, Tom Lane wrote: > >>> Bruce Momjian writes: > Modify pg_dump to use error-free memory allocation macros. This avoids > ignoring errors and call-site e

Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

2011-11-26 Thread Andrew Dunstan
On 11/26/2011 09:11 AM, Bruce Momjian wrote: \Andrew Dunstan wrote: On 11/26/2011 02:13 AM, Tom Lane wrote: Bruce Momjian writes: Modify pg_dump to use error-free memory allocation macros. This avoids ignoring errors and call-site error checking. This appears to have broken the MSVC bui

[COMMITTERS] pgsql: Fix join_path_components() to not add a leading slash when joini

2011-11-26 Thread Bruce Momjian
Fix join_path_components() to not add a leading slash when joining to an initial null string. Per report from Robert Haas in testing psql \ir. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/fd6dbc24ef1dc6b39a795b5e0e959cf500ad71d6 Modified Files -- src/

Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

2011-11-26 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > Modify pg_dump to use error-free memory allocation macros. This avoids > > ignoring errors and call-site error checking. > > This appears to have broken the MSVC build. More generally, I'd like to Doesn't the MSVC build scrape the Makefiles? Looking

Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

2011-11-26 Thread Bruce Momjian
\Andrew Dunstan wrote: > > > On 11/26/2011 02:13 AM, Tom Lane wrote: > > Bruce Momjian writes: > >> Modify pg_dump to use error-free memory allocation macros. This avoids > >> ignoring errors and call-site error checking. > > This appears to have broken the MSVC build. More generally, I'd like

Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

2011-11-26 Thread Andrew Dunstan
On 11/26/2011 02:13 AM, Tom Lane wrote: Bruce Momjian writes: Modify pg_dump to use error-free memory allocation macros. This avoids ignoring errors and call-site error checking. This appears to have broken the MSVC build. More generally, I'd like to object to arbitrarily moving a bunch of

[COMMITTERS] pgsql: Take fillfactor into account in the new COPY bulk heap insert co

2011-11-26 Thread Heikki Linnakangas
Take fillfactor into account in the new COPY bulk heap insert code. Jeff Janes Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dea5f6cefe74a6cb51a1cfd39e12a2e1a026df35 Modified Files -- src/backend/access/heap/heapam.c |5 - 1 files changed, 4 ins