Re: BUG #5171: Composite type with array does not translate in plpythonu

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jason <jason(at)beanfield(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5171: Composite type with array does not translate in plpythonu
Date: 2009-11-09 08:33:04
Message-ID: 1257755584.12918.0.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, 2009-11-08 at 16:33 -0500, Robert Haas wrote:
> On Sat, Nov 7, 2009 at 5:23 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > On fre, 2009-11-06 at 17:29 +0000, Jason wrote:
> >> When I have a plpythonu function returning a composite type that has an
> >> array column, the function does not work when I try to return a list for
> >> that column.
> >
> > There is a patch proposed to address that in 8.5, but before that,
> > arrays are pretty much not supported in plpythonu.
>
> Is this at all related to bug #5128?

It's in the same area, but fixing one won't fix the other, I think.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message digitaldeath 2009-11-09 09:48:27 Re: odd deadlock on CREATE TABLE AS SELECT
Previous Message Richard Neill 2009-11-09 01:04:08 Re: BUG #5174: [minor] directories symlinked into base/ are not recursively removed