Michael Fuhr wrote:
On Fri, Sep 23, 2005 at 05:03:02PM -0400, Bruce Momjian wrote:
Michael Fuhr wrote:
http://archives.postgresql.org/pgsql-patches/2005-06/msg00519.php
I have backpatched this to 8.0.X. It did not apply cleanly to 7.4.X so
if you would like that version patched
Michael Fuhr wrote:
On Mon, Jul 11, 2005 at 08:13:24PM -0600, Michael Fuhr wrote:
On Sun, Jul 10, 2005 at 12:58:24AM -0400, Bruce Momjian wrote:
I am unclear about backpatching this. We have to weigh the risks of
applying or not applying to 8.0.X. Comments?
Since 7.4, PL/Python is
On Fri, Sep 23, 2005 at 05:03:02PM -0400, Bruce Momjian wrote:
Michael Fuhr wrote:
http://archives.postgresql.org/pgsql-patches/2005-06/msg00519.php
I have backpatched this to 8.0.X. It did not apply cleanly to 7.4.X so
if you would like that version patched please submit a matching patch.
On Mon, Jul 11, 2005 at 08:13:24PM -0600, Michael Fuhr wrote:
On Sun, Jul 10, 2005 at 12:58:24AM -0400, Bruce Momjian wrote:
I am unclear about backpatching this. We have to weigh the risks of
applying or not applying to 8.0.X. Comments?
Since 7.4, PL/Python is only available as an
On Sun, Jul 10, 2005 at 12:58:24AM -0400, Bruce Momjian wrote:
Michael Fuhr wrote:
The patch is against HEAD but the same changes should be applied
to earlier versions because they have the same problem. The patch
might not apply cleanly against earlier versions -- will the committer
Michael Fuhr wrote:
This patch addresses the problem mentioned in the process crash
when a plpython function returns unicode thread:
http://archives.postgresql.org/pgsql-bugs/2005-06/msg00105.php
In several places PL/Python was calling PyObject_Str() and then
PyString_AsString() without
Patch applied. Thanks.
---
Michael Fuhr wrote:
This patch addresses the problem mentioned in the process crash
when a plpython function returns unicode thread:
This patch addresses the problem mentioned in the process crash
when a plpython function returns unicode thread:
http://archives.postgresql.org/pgsql-bugs/2005-06/msg00105.php
In several places PL/Python was calling PyObject_Str() and then
PyString_AsString() without checking if the former had
