Re: plpythonu and return void

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: aklaver(at)comcast(dot)net
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: plpythonu and return void
Date: 2005-08-09 03:02:17
Message-ID: 11643.1123556537@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <aklaver(at)comcast(dot)net> writes:
> I recently migrated a database from Postgres 7.4.1 to Postgres 8.03. The only
> problem I have run into is that a plpythonu function that returns void will
> not run under 8.03. The error message states that a plpython function cannot
> return void. I got around it by having it return text and not actually
> returning anything. I have searched for an explanation and can't seem to
> locate one.

The explanation is doubtless here:

2004-09-19 19:38 tgl

* src/pl/plpython/plpython.c: Add defenses against plpython
functions being declared to take or return pseudotypes. Not sure
why I neglected to add these checks at the same time I added them
to the other PLs, but it seems I did.

It's certainly possible to weaken this test to allow "void" again,
but shouldn't there be corresponding changes elsewhere to ensure that
the behavior is actually sensible?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ben 2005-08-09 06:39:25 Adjacency List & total item counts
Previous Message Adrian Klaver 2005-08-09 02:39:07 plpythonu and return void