Greetings,
The attached patch fixes a bug which was originally brought up in May
of 2002 in this thread:
http://archives.postgresql.org/pgsql-interfaces/2002-05/msg00083.php
The original bug reporter also supplied a patch to fix the problem:
On Wed, Feb 01, 2006 at 11:48:45PM -0500, Bruce Momjian wrote:
I have researched your report, and you are right, there are two ecpg
bugs here. First, dollar quoting uses single-quotes internally to do
the quoting, but it does not double any single-quotes in the
dollar-quoted string.
Actually
I have been working with plpython for several months and have
been hampered by the lack of a traceback being logged when a
plpython function raises an error. I have written a patch causes
the PLy_traceback function to fully log the traceback. The
output looks just like the traceback output
Tom,
I noticed in this thread:
http://archives.postgresql.org/pgsql-performance/2005-12/msg00206.php
you state:
Try something like -s 10 -c 10 -t 3000 to get numbers reflecting test
conditions more like what the TPC council had in mind when they designed
this benchmark. I tend to repeat such
Michael Meskes wrote:
On Wed, Feb 01, 2006 at 11:48:45PM -0500, Bruce Momjian wrote:
I have researched your report, and you are right, there are two ecpg
bugs here. First, dollar quoting uses single-quotes internally to do
the quoting, but it does not double any single-quotes in the
Here's a first draft patch for DROP ... IF EXISTS for the remaining
cases, namely: LANGUAGE, TABLESPACE, TRIGGER OPERATOR CLASS,
FUNCTION, AGGREGATE, OPERATOR, CAST and RULE.
At what point does this stop being useful and become mere bloat?
The only case I can ever recall being actually
Christopher Kings-Lynne wrote:
Here's a first draft patch for DROP ... IF EXISTS for the remaining
cases, namely: LANGUAGE, TABLESPACE, TRIGGER OPERATOR CLASS,
FUNCTION, AGGREGATE, OPERATOR, CAST and RULE.
At what point does this stop being useful and become mere bloat?
The only
Attached is a patch to the README file to bring it a little more up to
date with
current PostgreSQL.
12,14c12,23
The JDBC, ODBC, C++, Python, and Tcl interfaces have been moved to the
PostgreSQL Projects Web Site at http://gborg.postgresql.org for separate
maintenance. A Perl DBI/DBD driver
Is there a reason you didn't list the pl/PHP one? Seems appropriate for
that list no?
On Mon, 6 Feb 2006, Joshua D. Drake wrote:
Attached is a patch to the README file to bring it a little more up to date
with
current PostgreSQL.
Marc G. Fournier Hub.Org Networking
Marc G. Fournier wrote:
Is there a reason you didn't list the pl/PHP one? Seems appropriate
for that list no?
I was only listing client side interfaces... I could adapt to include
the PL interfaces.
Joshua D. Drake
On Mon, 6 Feb 2006, Joshua D. Drake wrote:
Attached is a patch to the
Marc G. Fournier wrote:
Is there a reason you didn't list the pl/PHP one? Seems appropriate
for that list no?
On Mon, 6 Feb 2006, Joshua D. Drake wrote:
adapted.
Attached is a patch to the README file to bring it a little more up
to date with
current PostgreSQL.
Marc G.
11 matches
Mail list logo
