Re: Bad behavior from plpython 'return []' - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Bad behavior from plpython 'return []'
Date
Msg-id CA+TgmoY7Oe1RQ3hJ9oHgYmz_D7PTjfYXbb3beLkW4bVBCpuW_Q@mail.gmail.com
Whole thread Raw
In response to Bad behavior from plpython 'return []'  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Bad behavior from plpython 'return []'  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jun 30, 2016 at 9:25 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> CREATE FUNCTION pg_temp.bad() RETURNS text[] LANGUAGE plpythonu AS $$return
> []$$;
> SELECT pg_temp.bad();
>  bad
> -----
>  {}
> (1 row)
>
> SELECT pg_temp.bad() = '{}'::text[];
>  ?column?
> ----------
>  f
> (1 row)
>
> Erm?? Turns out this is because
>
> SELECT array_dims(pg_temp.bad()), array_dims('{}'::text[]);
>  array_dims | array_dims
> ------------+------------
>  [1:0]      |
> (1 row)

Yeah, that's a bug.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: primary_conninfo missing from pg_stat_wal_receiver
Next
From: Tom Lane
Date:
Subject: Re: Broken handling of lwlocknames.h