Re: [COMMITTERS] pgsql: Add Unicode support in PL/Python PL/Python now accepts Unicode

[email protected] (Peter Eisentraut) writes: > Log Message: > --- > Add Unicode support in PL/Python The buildfarm seems quite unhappy with this patch. regards, tom lane -- Sent via pgsql-committers mailing list ([email protected]) To make chang

[COMMITTERS] pgsql: plug dblink resource leak dblink generates orphaned connections

Log Message: --- plug dblink resource leak dblink generates orphaned connections when called with a connection string, fail_on_error = true, and an ERROR occurs. Discovery and patch by Tatsuhito Kasahara. Introduced in 8.4. Tags: REL8_4_STABLE Modified Files: -- pgsq

[COMMITTERS] pgsql: plug dblink resource leak dblink generates orphaned connections

Log Message: --- plug dblink resource leak dblink generates orphaned connections when called with a connection string, fail_on_error = true, and an ERROR occurs. Discovery and patch by Tatsuhito Kasahara. Introduced in 8.4. Modified Files: -- pgsql/contrib/dblink:

[COMMITTERS] npgsql - Npgsql2: [#1010700] Capture parameter names with

Log Message: --- [#1010700] Capture parameter names with NpgsqlCommandBuilder.DeriveParameters. Thanks Brian Schloz (bschloz @nospam@ hotmail.com) for patch. Also added nunit testcase. Modified Files: -- Npgsql2/src/Npgsql: NpgsqlCommandBuilder.cs (r1.14 -> r1.15)

[COMMITTERS] pgsql: Add Unicode support in PL/Python PL/Python now accepts Unicode

Log Message: --- Add Unicode support in PL/Python PL/Python now accepts Unicode objects where it previously only accepted string objects (for example, as return value). Unicode objects are converted to the PostgreSQL server encoding as necessary. This change is also necessary for future

[COMMITTERS] pgsql: Rewrite the planner's handling of materialized plan types so that

Log Message: --- Rewrite the planner's handling of materialized plan types so that there is an explicit model of rescan costs being different from first-time costs. The costing of Material nodes in particular now has some visible relationship to the actual runtime behavior, where before it

Re: [COMMITTERS] Can not create more than 32766 databases in ufs file system.

Not sure that this really belongs on pgsql-committers - maybe pgsql-hackers? No matter what scheme PostgreSQL uses for storing the data, there can be underlying file system limitations. One solution, for example, would be to use a file system that does not have a limitation of 32k subdirectori

[COMMITTERS] Can not create more than 32766 databases in ufs file system.

Hi, pgsql-committers! I cannot created more than 32766 databases with freeBSD in one setup, not as the document says, "as many as you like". I found the problem is that the directory pgsql/data/base cannot hold more than 32766 subdirectories. I suggest to make 32766 subdirectories in base director

[COMMITTERS] pgsql: Improve GRANT reference page's description of object ownership

Log Message: --- Improve GRANT reference page's description of object ownership privileges by mentioning the possibility of granting membership in the owning role. Modified Files: -- pgsql/doc/src/sgml/ref: grant.sgml (r1.74 -> r1.75) (http://anoncvs.postgr

[COMMITTERS] pgsql: Install a hopefully-temporary workaround for Snow Leopard

Log Message: --- Install a hopefully-temporary workaround for Snow Leopard readdir() bug. If Apple doesn't fix that reasonably soon, we'll have to consider back-patching a workaround; but for now, just hack it in HEAD so that we can get buildfarm reports on HEAD from OS X machines. Per Jan

[COMMITTERS] pgsql: Remove TODO file; it has been added to the main Todo list in the

Log Message: --- Remove TODO file; it has been added to the main Todo list in the wiki. Removed Files: - pgsql/src/pl/plpython: TODO (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/TODO) -- Sent via pgsql-committers mailing list (pgsql-comm