Re: [COMMITTERS] pgsql: Add GUC temp_tablespaces to provide a default location for

2007-01-24 Thread Jaime Casanova
On 1/24/07, Bruce Momjian <[EMAIL PROTECTED]> wrote: Log Message: --- Add GUC temp_tablespaces to provide a default location for temporary objects. Jaime Casanova the credit is for Albert Cervera Areny, I just did some minor revisions and documentation: http://archives.postgresql.org

Re: [COMMITTERS] pgsql: Fix for plpython functions; return true/false for boolean,

2007-01-24 Thread Tom Lane
[EMAIL PROTECTED] (Bruce Momjian) writes: > Fix for plpython functions; return true/false for boolean, This patch has broken a majority of the buildfarm. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked ou

[COMMITTERS] pgsql: Done: > o -Add a GUC variable to control the tablespace for

2007-01-24 Thread Bruce Momjian
Log Message: --- Done: > o -Add a GUC variable to control the tablespace for temporary objects Modified Files: -- pgsql/doc: TODO (r1.2049 -> r1.2050) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2049&r2=1.2050) pgsql/doc/

[COMMITTERS] pgsql: Add GUC temp_tablespaces to provide a default location for

2007-01-24 Thread Bruce Momjian
Log Message: --- Add GUC temp_tablespaces to provide a default location for temporary objects. Jaime Casanova Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.104 -> r1.105) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.d

[COMMITTERS] pgsql: Properly detoast access to bytea field pg_trigger.tgargs.

2007-01-24 Thread Bruce Momjian
Log Message: --- Properly detoast access to bytea field pg_trigger.tgargs. Old code might cause server crash. Backpatch to 8.2.X. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/backend/commands: tablecmds.c (r1.206 -> r1.206.2.1) (http://developer

[COMMITTERS] pgsql: Properly detoast access to bytea field pg_trigger.tgargs.

2007-01-24 Thread Bruce Momjian
Log Message: --- Properly detoast access to bytea field pg_trigger.tgargs. Old code might cause server crash. Backpatch to 8.2.X. Modified Files: -- pgsql/src/backend/commands: tablecmds.c (r1.210 -> r1.211) (http://developer.postgresql.org/cvsweb.cgi/pgs

[COMMITTERS] pgsql: Fix for plpython functions; return true/false for boolean,

2007-01-24 Thread Bruce Momjian
Log Message: --- Fix for plpython functions; return true/false for boolean, rather than 1/0. This helps when creating trigger functions that output SQL. Guido Goldstein Modified Files: -- pgsql/src/pl/plpython: plpython.c (r1.90 -> r1.91) (http://develop

[COMMITTERS] pgsql: Add 'output file' option for pg_dumpall, especially useful for

2007-01-24 Thread Bruce Momjian
Log Message: --- Add 'output file' option for pg_dumpall, especially useful for Win32, where output redirection of child processes (pg_dump) doesn't work. Dave Page Modified Files: -- pgsql/doc/src/sgml/ref: pg_dumpall.sgml (r1.61 -> r1.62) (http://develop

[COMMITTERS] pgsql: Remove developers list from TODO list now that we have URLs to

2007-01-24 Thread Bruce Momjian
Log Message: --- Remove developers list from TODO list now that we have URLs to reference discussions. < < < --- < < < Developers who have claimed items are: < -- < * Alvaro is A

[COMMITTERS] pgsql: Done: < o Add -f to pg_dumpall > o -Add -f to pg_dumpall

2007-01-24 Thread Bruce Momjian
Log Message: --- Done: < o Add -f to pg_dumpall > o -Add -f to pg_dumpall Modified Files: -- pgsql/doc: TODO (r1.2047 -> r1.2048) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2047&r2=1.2048) pgsql/doc/src/FAQ:

[COMMITTERS] pgsql: Allow pg_dumpall to specify a database name rather than the

2007-01-24 Thread Bruce Momjian
Log Message: --- Allow pg_dumpall to specify a database name rather than the default 'template1'. Dave Page Modified Files: -- pgsql/doc/src/sgml/ref: pg_dumpall.sgml (r1.60 -> r1.61) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_du

[COMMITTERS] pgsql: Add --tablespaces-only and --roles-only options to pg_dumpall.

2007-01-24 Thread Bruce Momjian
Log Message: --- Add --tablespaces-only and --roles-only options to pg_dumpall. Dave Page Modified Files: -- pgsql/doc/src/sgml/ref: pg_dumpall.sgml (r1.59 -> r1.60) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_dumpall.sgml.diff?r1

[COMMITTERS] pgsql: Prevent WAL logging when COPY is done in the same transation that

2007-01-24 Thread Bruce Momjian
Log Message: --- Prevent WAL logging when COPY is done in the same transation that created it. Simon Riggs Modified Files: -- pgsql/doc/src/sgml: perform.sgml (r1.59 -> r1.60) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/perform.sgml.dif

[COMMITTERS] pgsql: When using MSVC, disable the building of ecpg if pthreads is not

2007-01-24 Thread Bruce Momjian
Log Message: --- When using MSVC, disable the building of ecpg if pthreads is not specified. Magnus Hagander Modified Files: -- pgsql/src/tools/msvc: Project.pm (r1.6 -> r1.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/Project.pm.diff

[COMMITTERS] pgsql: Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on

2007-01-24 Thread Tom Lane
Log Message: --- Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on the same page about the maximum UTF8 sequence length we support (4 bytes since 8.1, 3 before that). pg_utf2wchar_with_len never got updated to support 4-byte characters at all, and in any case had a buffer-o

[COMMITTERS] pgsql: Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on

2007-01-24 Thread Tom Lane
Log Message: --- Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on the same page about the maximum UTF8 sequence length we support (4 bytes since 8.1, 3 before that). pg_utf2wchar_with_len never got updated to support 4-byte characters at all, and in any case had a buffer-o

[COMMITTERS] pgsql: Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on

2007-01-24 Thread Tom Lane
Log Message: --- Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on the same page about the maximum UTF8 sequence length we support (4 bytes since 8.1, 3 before that). pg_utf2wchar_with_len never got updated to support 4-byte characters at all, and in any case had a buffer-o

[COMMITTERS] pgsql: Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on

2007-01-24 Thread Tom Lane
Log Message: --- Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on the same page about the maximum UTF8 sequence length we support (4 bytes since 8.1, 3 before that). pg_utf2wchar_with_len never got updated to support 4-byte characters at all, and in any case had a buffer-o

[COMMITTERS] pgsql: Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on

2007-01-24 Thread Tom Lane
Log Message: --- Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on the same page about the maximum UTF8 sequence length we support (4 bytes since 8.1, 3 before that). pg_utf2wchar_with_len never got updated to support 4-byte characters at all, and in any case had a buffer-o

[COMMITTERS] pgsql: Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on

2007-01-24 Thread Tom Lane
Log Message: --- Get pg_utf_mblen(), pg_utf2wchar_with_len(), and utf2ucs() all on the same page about the maximum UTF8 sequence length we support (4 bytes since 8.1, 3 before that). pg_utf2wchar_with_len never got updated to support 4-byte characters at all, and in any case had a buffer-o