[COMMITTERS] psqlodbc - psqlodbc: - skip QR_fetch_tuples when backend returns

2005-12-02 Thread User Dpage
Log Message: --- - skip QR_fetch_tuples when backend returns PGRES_COMMAND_OK - there is no data to fetch - add support for returning rowcount from select statements (with UseDeclareFetch disabled - as non-libpq versions) - add some mylog output for better tracing [Ludek Finstrle] Modifi

[COMMITTERS] psqlodbc - psqlodbc: Formatting cleanup.

2005-12-02 Thread User Dpage
Log Message: --- Formatting cleanup. Reenable Luf's verbose logging. Modified Files: -- psqlodbc: connection.c (r1.123 -> r1.124) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.c.diff?r1=1.123&r2=1.124) --

[COMMITTERS] pgsql: Added special handling of CONNECTION variable that is used by

2005-12-02 Thread Michael Meskes
Log Message: --- Added special handling of CONNECTION variable that is used by ECPG instead of given to the backend. Modified Files: -- pgsql/src/interfaces/ecpg: ChangeLog (r1.295 -> r1.296) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces

[COMMITTERS] pgsql: Added special handling of CONNECTION variable that is used by

2005-12-02 Thread Michael Meskes
Log Message: --- Added special handling of CONNECTION variable that is used by ECPG instead of given to the backend. I failed to notice that CONNECTION had become a keyword in 8.1. Tags: REL8_1_STABLE Modified Files: -- pgsql/src/interfaces/ecpg/preproc: ecpg

[COMMITTERS] pgsql: Remove idea of increasing NUMERIC length: < * Change NUMERIC to

2005-12-02 Thread Bruce Momjian
Log Message: --- Remove idea of increasing NUMERIC length: < * Change NUMERIC to enforce the maximum precision, and increase it > * Change NUMERIC to enforce the maximum precision Modified Files: -- pgsql/doc: TODO (r1.1710 -> r1.1711) (http://developer.po

[COMMITTERS] pgsql: Adjust scan plan nodes to avoid getting an extra AccessShareLock

2005-12-02 Thread Tom Lane
Log Message: --- Adjust scan plan nodes to avoid getting an extra AccessShareLock on a relation if it's already been locked by execMain.c as either a result relation or a FOR UPDATE/SHARE relation. This avoids an extra trip to the shared lock manager state. Per my suggestion yesterday. M

[COMMITTERS] psqlodbc - psqlodbc: Make sure data_at_exec parameters are cleared by

2005-12-02 Thread User Dpage
Log Message: --- Make sure data_at_exec parameters are cleared by SQLCancel {Dave Page & Ludek Finstrle, with test case from Andrus] Modified Files: -- psqlodbc: execute.c (r1.72 -> r1.73) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/exec

[COMMITTERS] pgsql: Fix obsolete comment.

2005-12-02 Thread Tom Lane
Log Message: --- Fix obsolete comment. Modified Files: -- pgsql/src/bin/pg_dump: dumputils.c (r1.21 -> r1.22) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/dumputils.c.diff?r1=1.21&r2=1.22) ---(end of broadcast)-

[COMMITTERS] pgsql: Fix obsolete description of -h option, per Andreas Schmidt.

2005-12-02 Thread Tom Lane
Log Message: --- Fix obsolete description of -h option, per Andreas Schmidt. Modified Files: -- pgsql/doc/src/sgml/ref: postmaster.sgml (r1.53 -> r1.54) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/postmaster.sgml.diff?r1=1.53&r2=1.54)

[COMMITTERS] pgsql: Fix obsolete description of -h option, per Andreas Schmidt.

2005-12-02 Thread Tom Lane
Log Message: --- Fix obsolete description of -h option, per Andreas Schmidt. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml/ref: postmaster.sgml (r1.53 -> r1.53.6.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/postmas

[COMMITTERS] pgsql: Fix obsolete description of -h option, per Andreas Schmidt.

2005-12-02 Thread Tom Lane
Log Message: --- Fix obsolete description of -h option, per Andreas Schmidt. Tags: REL8_0_STABLE Modified Files: -- pgsql/doc/src/sgml/ref: postmaster.sgml (r1.53 -> r1.53.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/postmas

[COMMITTERS] pgsql: Tweak indexscan machinery to avoid taking an AccessShareLock on

2005-12-02 Thread Tom Lane
Log Message: --- Tweak indexscan machinery to avoid taking an AccessShareLock on an index if we already have a stronger lock due to the index's table being the update target table of the query. Same optimization I applied earlier at the table level. There doesn't seem to be much interest