Log Message:
---
Feature list update
Modified Files:
--
pgsql/src/backend/catalog:
sql_features.txt (r1.26 -> r1.27)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/sql_features.txt?r1=1.26&r2=1.27)
--
Sent via pgsql-committers mailing
Log Message:
---
Allow EXPLAIN on CREATE TABLE AS.
Modified Files:
--
pgsql/doc/src/sgml/ref:
explain.sgml (r1.42 -> r1.43)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/explain.sgml?r1=1.42&r2=1.43)
pgsql/src/backend/parser:
Log Message:
---
Update standalong libpq makefiles for msvc and bcc to work with the new
libpq events code.
Hiroshi Saito
Modified Files:
--
pgsql/src/interfaces/libpq:
bcc32.mak (r1.30 -> r1.31)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfac
Log Message:
---
SQL:2008 syntax CURRENT_CATALOG, CURRENT_SCHEMA, SET CATALOG, SET SCHEMA.
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.450 -> r1.451)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml?r1=1.450&r2=1.451)
pgsq
Log Message:
---
Add support for multiple error messages from libpq, by simply appending them
after each other (since we already add a newline on each, this makes them
multiline).
Previously a new error would just overwrite the old one, so for example any
error caused when trying to connec
Log Message:
---
Changed tabs to spaces 4
Modified Files:
--
Npgsql2/src/NpgsqlTypes:
NpgsqlTypes.cs (r1.7 -> r1.8)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/NpgsqlTypes/NpgsqlTypes.cs.diff?r1=1.7&r2=1.8)
--
Sent via pgsql-committer
Log Message:
---
Changed public fields into properties. Miguel de Icaza from Mono project asked
for this change because previous versions of Npgsql used to have properties and
this change could break existing clients.
Modified Files:
--
Npgsql2/src/NpgsqlTypes:
N
Log Message:
---
asynctest: compat for CASSERT builds
Tags:
pgbouncer_1_2_stable
Modified Files:
--
pgbouncer/test:
asynctest.c (r1.13 -> r1.13.2.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/test/asynctest.c.diff?r1=1.13&r2=1.13
Log Message:
---
log warning if timer problem
Tags:
pgbouncer_1_2_stable
Modified Files:
--
pgbouncer/src:
util.c (r1.24 -> r1.24.2.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/util.c.diff?r1=1.24&r2=1.24.2.1)
--
Sent via
Log Message:
---
Changed at Miguel's request to provide same constructors and properties as
previous version of Npgsql in order to not break existing code.
Modified Files:
--
Npgsql2/src/NpgsqlTypes:
NpgsqlTypes.cs (r1.9 -> r1.10)
(http://cvs.pgfoundry.or
Log Message:
---
Install a more robust solution for the problem of infinite error-processing
recursion when we are unable to convert a localized error message to the
client's encoding. We've been over this ground before, but as reported by
Ibrar Ahmed, it still didn't work in the case of c
Log Message:
---
Install a more robust solution for the problem of infinite error-processing
recursion when we are unable to convert a localized error message to the
client's encoding. We've been over this ground before, but as reported by
Ibrar Ahmed, it still didn't work in the case of c
Log Message:
---
Install a more robust solution for the problem of infinite error-processing
recursion when we are unable to convert a localized error message to the
client's encoding. We've been over this ground before, but as reported by
Ibrar Ahmed, it still didn't work in the case of c
Log Message:
---
Install a more robust solution for the problem of infinite error-processing
recursion when we are unable to convert a localized error message to the
client's encoding. We've been over this ground before, but as reported by
Ibrar Ahmed, it still didn't work in the case of c
Log Message:
---
Install a more robust solution for the problem of infinite error-processing
recursion when we are unable to convert a localized error message to the
client's encoding. We've been over this ground before, but as reported by
Ibrar Ahmed, it still didn't work in the case of c
Log Message:
---
Install a more robust solution for the problem of infinite error-processing
recursion when we are unable to convert a localized error message to the
client's encoding. We've been over this ground before, but as reported by
Ibrar Ahmed, it still didn't work in the case of c
Log Message:
---
Make hba parsing error messages more specific.
Modified Files:
--
pgsql/src/backend/libpq:
hba.c (r1.170 -> r1.171)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/hba.c?r1=1.170&r2=1.171)
--
Sent via pgsql-committers ma
Log Message:
---
No need for extra code to log freezing zero tuples. Callers already check that
they are freezing a nonzero amount anyway.
Modified Files:
--
pgsql/src/backend/access/heap:
heapam.c (r1.265 -> r1.266)
(http://anoncvs.postgresql.org/cvsweb.c
Log Message:
---
Downgrade can't-happen error reports to elog().
Modified Files:
--
pgsql/src/backend/utils/time:
snapmgr.c (r1.5 -> r1.6)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/snapmgr.c?r1=1.5&r2=1.6)
--
Sent via pgsql-co
Log Message:
---
Now works on 8.2; remove concat() overloads on 8.2.
Modified Files:
--
orafce:
INSTALL.orafunc (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/INSTALL.orafunc.diff?r1=1.3&r2=1.4)
orafunc.sql.in (r1.45 -> r1
20 matches
Mail list logo
