From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql@groks.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Type implemented in plpythonu crashes backend
Date: Sun, 15 Aug 2004 15:02:10 -0400
Message-ID: <28793.1092596530@sss.pgh.pa.us> (raw)
In-Reply-To: <1092210515.2350.100.camel@january.e-complex.ca>
References: <1092210515.2350.100.camel@january.e-complex.ca>
pgsql@groks.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql@groks.org
Subject: Re: Type implemented in plpythonu crashes backend
In-Reply-To: <28793.1092596530@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox