From: | Jan Urbański <wulczer(at)wulczer(dot)org> |
---|---|
To: | Jean-Baptiste Quenot <jbq(at)caraldi(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: plpython crash |
Date: | 2011-08-16 15:06:37 |
Message-ID: | 4E4A877D.3000700@wulczer.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16/08/11 16:52, Jean-Baptiste Quenot wrote:
> After backporting plpython.c from HEAD, this is the error message I get:
>
> ERROR: key "........pg.dropped.6........" not found in mapping
> HINT: To return null in a column, add the value None to the mapping
> with the key named after the column.
> CONTEXT: while creating return value
> PL/Python function "myfunc"
>
> What does it mean?
Ah, interesting, I think that this means that you are returning a table
type and that table has a dropped column. The code should skip over
dropped columns, but apparently it does not and tries to find a value
for that column in the mapping you are returning.
I'll try to reproduce it here.
Jan
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2011-08-16 15:22:15 | Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs? |
Previous Message | Magnus Hagander | 2011-08-16 15:00:10 | pgsql: Adjust total size in pg_basebackup progress report when reality |