Re: Type implemented in plpythonu crashes backend

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql(at)groks(dot)org
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Type implemented in plpythonu crashes backend
Date: 2004-08-15 19:02:10
Message-ID: 28793.1092596530@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

pgsql(at)groks(dot)org writes:
> I'd like to implement new postgres types in a language other than C for
> prototyping speed. plpgsql won't let me create a function which takes a
> cstring, and neither will pltcl. Happily, plpythonu will, and it seems
> to work fine.

I'd say this is an oversight in the plpython code --- it should be
rejecting pseudotype arguments, since as you've discovered it cannot
really cope. It should *certainly* reject "opaque" ... might be okay to
allow cstring but I'm not sure.

regards, tom lane

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Richard Welty 2004-08-15 20:35:07 Re: Calling C++ function
Previous Message Tom Lane 2004-08-15 18:27:38 Re: Calling C++ function