Re: [COMMITTERS] pgsql: Update release notes.

2006-02-13 Thread Teodor Sigaev
> Improve speed of /contrib/tsearch2 index creation (Teodor) It was you, not me :) -- Teodor Sigaev E-mail: [EMAIL PROTECTED] WWW: http://www.sigaev.ru/ ---(end of broadcast)---

[COMMITTERS] pginstaller - pginst: Updates for 8.0.7

2006-02-13 Thread User Dpage
Log Message: --- Updates for 8.0.7 Tags: REL8_0_STABLE Modified Files: -- pginst/package: README.TXT (r1.1.2.6 -> r1.1.2.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/package/README.TXT.diff?r1=1.1.2.6&r2=1.1.2.7) upgrade.

[COMMITTERS] pgsql: Fix build failure when not USE_READLINE.

2006-02-13 Thread Tom Lane
Log Message: --- Fix build failure when not USE_READLINE. Sergey E. Koposov Modified Files: -- pgsql/src/bin/psql: input.c (r1.48 -> r1.49) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/input.c.diff?r1=1.48&r2=1.49) --

[COMMITTERS] pgsql: Fix qual_is_pushdown_safe to not try to push down quals involving

2006-02-13 Thread Tom Lane
Log Message: --- Fix qual_is_pushdown_safe to not try to push down quals involving a whole-row Var referencing the subselect output. While this case could possibly be made to work, it seems not worth expending effort on. Per report from Magnus Naeslund(f). Modified Files: --

[COMMITTERS] pgsql: Place function names in first column for consistency.

2006-02-13 Thread Bruce Momjian
Log Message: --- Place function names in first column for consistency. Modified Files: -- pgsql/src/bin/psql: input.c (r1.49 -> r1.50) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/input.c.diff?r1=1.49&r2=1.50) ---(

[COMMITTERS] python - be: Link against LIBS var to make Python happy.

2006-02-13 Thread James William Pye
Log Message: --- Link against LIBS var to make Python happy. This should fix missing symbols issues on load. Modified Files: -- be: setup.py (r1.22 -> r1.23) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/setup.py.diff?r1=1.22&r2=1.23) ---

[COMMITTERS] pgsql: Fix qual_is_pushdown_safe to not try to push down quals involving

2006-02-13 Thread Tom Lane
Log Message: --- Fix qual_is_pushdown_safe to not try to push down quals involving a whole-row Var referencing the subselect output. While this case could possibly be made to work, it seems not worth expending effort on. Per report from Magnus Naeslund(f). Tags: REL8_0_STABLE Modif

[COMMITTERS] pgsql: Fix qual_is_pushdown_safe to not try to push down quals involving

2006-02-13 Thread Tom Lane
Log Message: --- Fix qual_is_pushdown_safe to not try to push down quals involving a whole-row Var referencing the subselect output. While this case could possibly be made to work, it seems not worth expending effort on. Per report from Magnus Naeslund(f). Tags: REL8_1_STABLE Modif

Re: [COMMITTERS] pgsql: Add psql option: -1 or --single-transaction Simon Riggs

2006-02-13 Thread Tom Lane
Isn't this patch emitting the BEGIN at the wrong place? -- -- PostgreSQL database dump -- SET client_encoding = 'SQL_ASCII'; SET check_function_bodies = false; SET client_min_messages = warning; BEGIN; -- -- Name: SCHEMA public; Type: COMMENT; Schema: -; Owner: postgres -- COMMENT ON SCHEMA pu

[COMMITTERS] pgsql: Improve documentation of --single-transaction option: fix markup,

2006-02-13 Thread Tom Lane
Log Message: --- Improve documentation of --single-transaction option: fix markup, and don't promise more than the code actually delivers. Modified Files: -- pgsql/doc/src/sgml/ref: pg_restore.sgml (r1.57 -> r1.58) (http://developer.postgresql.org/cvsweb.cg

[COMMITTERS] pgsql: IMHO, --single-transaction should wrap *all* the commands in

2006-02-13 Thread Tom Lane
Log Message: --- IMHO, --single-transaction should wrap *all* the commands in BEGIN/COMMIT, not just some of them. Modified Files: -- pgsql/src/bin/pg_dump: pg_backup_archiver.c (r1.123 -> r1.124) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg

[COMMITTERS] pgsql: Add positive defense against trying to connect when the

2006-02-13 Thread Tom Lane
Log Message: --- Add positive defense against trying to connect when the connection option state hasn't been fully set up. This is possible via PQreset() and might occur in other code paths too, so a state flag seems the most robust solution. Per report from Arturs Zoldners. Modified Fil

Re: [COMMITTERS] pgsql: Add psql option: -1 or --single-transaction

2006-02-13 Thread Christopher Kings-Lynne
BEGIN; -- -- Name: SCHEMA public; Type: COMMENT; Schema: -; Owner: postgres -- COMMENT ON SCHEMA public IS 'Standard public schema'; That's not what I would call guaranteeing that all the commands execute successfully. What if the client encoding is unrecognized, for instance? How does this

[COMMITTERS] pgsql: Document that xact commit/abort stats are collected if any stat

2006-02-13 Thread Bruce Momjian
Log Message: --- Document that xact commit/abort stats are collected if any stat variable is set. Modified Files: -- pgsql/doc/src/sgml: monitoring.sgml (r1.29 -> r1.30) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/monitoring.sgml.diff?r1=

[COMMITTERS] bizgres - bizgres: Added error debug information when transactions fail.

2006-02-13 Thread User Agoldshuv
Log Message: --- Added error debug information when transactions fail. Modified Files: -- bizgres/loader/src/native/com/deepgreen/loader: lipqcmd.c (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/loader/src/native/com/deepgreen/l

[COMMITTERS] python - fe: Reduce the identifier size for prepared statements.

2006-02-13 Thread James William Pye
Log Message: --- Reduce the identifier size for prepared statements. In, at least one, 7.4 there seems to be a more significant limitation on the size of the statement identifier string, so go ahead and cut the size on all identifiers. (Really, it doesn't need to be so long to begin with a

[COMMITTERS] bizgres - bizgres: Multiple LOAD statements in one control file are now

2006-02-13 Thread User Agoldshuv
Log Message: --- Multiple LOAD statements in one control file are now working again... Modified Files: -- bizgres/loader/src/com/deepgreen/loader: DGLoader.java (r1.13 -> r1.14) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/loader/src/com/dee

[COMMITTERS] pgsql: Document that GRANT on a table does not affect sequence

2006-02-13 Thread Bruce Momjian
Log Message: --- Document that GRANT on a table does not affect sequence permissions, inclusing SERIAL column sequences. Modified Files: -- pgsql/doc/src/sgml/ref: grant.sgml (r1.51 -> r1.52) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/re

Re: [COMMITTERS] pgsql: Add psql option: -1 or --single-transaction Simon Riggs

2006-02-13 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: > How does this interact with the begin/commit placed around LOB dumps? Good question ... right offhand it looks like there are some broken things there (try grepping bin/pg_dump/ for BEGIN). regards, tom lane --

Re: [COMMITTERS] pgsql: Add psql option: -1 or --single-transaction

2006-02-13 Thread Christopher Kings-Lynne
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: How does this interact with the begin/commit placed around LOB dumps? Good question ... right offhand it looks like there are some broken things there (try grepping bin/pg_dump/ for BEGIN). I suggest you just suppress the begin/commit for ea

Re: [COMMITTERS] pgsql: Add psql option: -1 or --single-transaction

2006-02-13 Thread Christopher Kings-Lynne
Good question ... right offhand it looks like there are some broken things there (try grepping bin/pg_dump/ for BEGIN). I suggest you just suppress the begin/commit for each LOB if --single-transaction is specified, as it'd be in a single transaction anyway... Or...it could create and relea