Re: [COMMITTERS] pgsql: Make the pg_stat_activity view call a SRF

2008-08-15 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Magnus Hagander wrote: >> Bruce Momjian wrote: >>> * Fix system views like pg_stat_all_tables to use set-returning >>> functions, rather than views of per-column functions >> >> Thanks, and while I approve of that TODO, that's not actually the one I >> w

Re: [COMMITTERS] pgsql: Make the pg_stat_activity view call a SRF

2008-08-15 Thread Bruce Momjian
Magnus Hagander wrote: > Bruce Momjian wrote: > > Magnus Hagander wrote: > >>> Sure, see pg_timezone_abbrevs(), pg_timezone_names(). > >>> > >>> (This only started to work recently, which is why we have so many > >>> record-returning functions that don't do it that way. It might be > >>> an idea t

[COMMITTERS] npgsql - Npgsql2: added support for uuid type

2008-08-15 Thread User Jbcooley
Log Message: --- added support for uuid type Modified Files: -- Npgsql2/src/Npgsql: NpgsqlProviderManifest.Manifest.xml (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlProviderManifest.Manifest.xml.diff?r1=1.4&r2=

[COMMITTERS] npgsql - Npgsql2: update precision to int4.

2008-08-15 Thread User Jbcooley
Log Message: --- update precision to int4. Modified Files: -- Npgsql2/src/Npgsql: NpgsqlSchema.ssdl (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlSchema.ssdl.diff?r1=1.4&r2=1.5) -- Sent via pgsql-committers ma

[COMMITTERS] pgsql: Add URL for: * Improve ability to modify views via ALTER TABLE

2008-08-15 Thread Bruce Momjian
Log Message: --- Add URL for: * Improve ability to modify views via ALTER TABLE < > http://archives.postgresql.org/pgsql-hackers/2008-08/msg00300.php Modified Files: -- pgsql/doc: TODO (r1.2497 -> r1.2498) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql

[COMMITTERS] pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably

2008-08-15 Thread Tom Lane
Log Message: --- Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec returns NULL instead of a PGresult. The former coding would fail, which is OK, but it neglected to give you the PQerrorMessage that might tell you why. In the oldest branches, there was another prob

[COMMITTERS] pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably

2008-08-15 Thread Tom Lane
Log Message: --- Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec returns NULL instead of a PGresult. The former coding would fail, which is OK, but it neglected to give you the PQerrorMessage that might tell you why. In the oldest branches, there was another prob

[COMMITTERS] pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably

2008-08-15 Thread Tom Lane
Log Message: --- Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec returns NULL instead of a PGresult. The former coding would fail, which is OK, but it neglected to give you the PQerrorMessage that might tell you why. In the oldest branches, there was another prob

[COMMITTERS] pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably

2008-08-15 Thread Tom Lane
Log Message: --- Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec returns NULL instead of a PGresult. The former coding would fail, which is OK, but it neglected to give you the PQerrorMessage that might tell you why. In the oldest branches, there was another prob

[COMMITTERS] pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably

2008-08-15 Thread Tom Lane
Log Message: --- Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec returns NULL instead of a PGresult. The former coding would fail, which is OK, but it neglected to give you the PQerrorMessage that might tell you why. In the oldest branches, there was another prob

[COMMITTERS] pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably

2008-08-15 Thread Tom Lane
Log Message: --- Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec returns NULL instead of a PGresult. The former coding would fail, which is OK, but it neglected to give you the PQerrorMessage that might tell you why. In the oldest branches, there was another prob

[COMMITTERS] pgsql: Add to TODO: > > * Prevent query cancel packets from being

2008-08-15 Thread Bruce Momjian
Log Message: --- Add to TODO: > > * Prevent query cancel packets from being replayed by an attacker, > especially when using SSL > > http://archives.postgresql.org/pgsql-hackers/2008-08/msg00345.php > Modified Files: -- pgsql/doc: TODO (r1.2496 -> r1.2497)

[COMMITTERS] pgsql: Synchronize Borland libpq makefile to match MSVC.

2008-08-15 Thread Bruce Momjian
Log Message: --- Synchronize Borland libpq makefile to match MSVC. Backpatch to 8.3.X. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/interfaces/libpq: bcc32.mak (r1.28 -> r1.28.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/li

[COMMITTERS] pgsql: Synchronize Borland libpq makefile to match MSVC.

2008-08-15 Thread Bruce Momjian
Log Message: --- Synchronize Borland libpq makefile to match MSVC. Backpatch to 8.3.X. Modified Files: -- pgsql/src/interfaces/libpq: bcc32.mak (r1.29 -> r1.30) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/bcc32.mak?r1=1.29&r2=1.30)

[COMMITTERS] npgsql - Npgsql2: [#1010401] uuid data type not parsed correctly to

2008-08-15 Thread User Fxjr
Log Message: --- [#1010401] uuid data type not parsed correctly to it's native .NET type. Added test which confirms this bug is fixed. Modified Files: -- Npgsql2/testsuite/noninteractive/NUnit20: CommandTests.cs (r1.13 -> r1.14) (http://cvs.pgfoundry.org/c

[COMMITTERS] pgsql: Fix a couple of places where psql might fail to report a suitable

2008-08-15 Thread Tom Lane
Log Message: --- Fix a couple of places where psql might fail to report a suitable error if PQexec returns NULL. These don't seem significant enough to be worth back-patching, but they ought to get fixed ... Modified Files: -- pgsql/src/bin/psql: common.c (r1.139 -

[COMMITTERS] pgsql: Update Russian FAQ.

2008-08-15 Thread Bruce Momjian
Log Message: --- Update Russian FAQ. [EMAIL PROTECTED] Modified Files: -- pgsql/doc: FAQ_russian (r1.30 -> r1.31) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_russian?r1=1.30&r2=1.31) pgsql/doc/src/FAQ: FAQ_russian.html (r1.33 -> r1.

[COMMITTERS] pgsql: Add new SQL training web site to FAQ:

2008-08-15 Thread Bruce Momjian
Log Message: --- Add new SQL training web site to FAQ: http://sqlzoo.net";>http://sqlzoo.net Modified Files: -- pgsql/doc: FAQ (r1.460 -> r1.461) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ?r1=1.460&r2=1.461) pgsql/doc/src/FAQ:

[COMMITTERS] pgsql: Fix version warning bug in recently applied adjustments to psql

2008-08-15 Thread Bruce Momjian
Log Message: --- Fix version warning bug in recently applied adjustments to psql startup. Gregory Stark Modified Files: -- pgsql/src/bin/psql: command.c (r1.192 -> r1.193) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c?r1=1.192&r2=1

[COMMITTERS] pgsql: Clean up the loose ends in selectivity estimation left by my

2008-08-15 Thread Tom Lane
Log Message: --- Clean up the loose ends in selectivity estimation left by my patch for semi and anti joins. To do this, pass the SpecialJoinInfo struct for the current join as an additional optional argument to operator join selectivity estimation functions. This allows the estimator to

[COMMITTERS] pgsql: Performance fix for new anti-join code in nodeMergejoin.c: after

2008-08-15 Thread Tom Lane
Log Message: --- Performance fix for new anti-join code in nodeMergejoin.c: after finding a match in antijoin mode, we should advance to next outer tuple not next inner. We know we don't want to return this outer tuple, and there is no point in advancing over matching inner tuples now, beca

[COMMITTERS] stackbuilder - wizard: Remove extra bracket

2008-08-15 Thread Dave Page
Log Message: --- Remove extra bracket Modified Files: -- wizard: CMakeLists.txt (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/CMakeLists.txt.diff?r1=1.9&r2=1.10) -- Sent via pgsql-committers mailing list (pgsql-committer

[COMMITTERS] stackbuilder - wizard: Ensure the executable bit is set appropriately

2008-08-15 Thread Dave Page
Log Message: --- Ensure the executable bit is set appropriately Modified Files: -- wizard: CMakeLists.txt (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/CMakeLists.txt.diff?r1=1.8&r2=1.9) -- Sent via pgsql-committers maili

[COMMITTERS] stackbuilder - wizard: It's kinda useful if we actually install the

2008-08-15 Thread Dave Page
Log Message: --- It's kinda useful if we actually install the binary as well as the message catalogs :-p Modified Files: -- wizard: CMakeLists.txt (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/CMakeLists.txt.diff?r1=1.7&r2

[COMMITTERS] pgsql: Make the temporary directory for pgstat files configurable by the

2008-08-15 Thread Magnus Hagander
Log Message: --- Make the temporary directory for pgstat files configurable by the GUC variable stats_temp_directory, instead of requiring the admin to mount/symlink the pg_stat_tmp directory manually. For now the config variable is PGC_POSTMASTER. Room for further improvment that would al