Skip site navigation (1) Skip section navigation (2)

Re: Type implemented in plpythonu crashes backend

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql(at)groks(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Type implemented in plpythonu crashes backend
Date: 2004-08-17 02:45:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Added to open items list:

	* have plpython reject pseudotype arguments because it crashes


Tom Lane wrote:
> 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
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-interfaces by date

Next:From: Paul TillesDate: 2004-08-20 12:25:48
Subject: Version 7.4.4
Previous:From: Tom LaneDate: 2004-08-16 14:34:25
Subject: Re: C text to string issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group