| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pierre-Yves LANDURE <pylandur(at)ifremer(dot)fr> |
| Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Polygon contrib |
| Date: | 2002-08-08 07:20:11 |
| Message-ID: | 837.1028791211@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Pierre-Yves LANDURE <pylandur(at)ifremer(dot)fr> writes:
> (gdb) bt
> #0 0x08152bd9 in pg_detoast_datum ()
> #1 0x4001ab72 in poly_center () from
> /usr/lib/postgresql/lib/polygons_utils.so
> #2 0x08151c5e in fmgr_internal_function ()
> #3 0x080c50bd in ExecMakeFunctionResult ()
Hm. And the query that triggers this is what exactly?
Judging from the stack trace, this cannot be poly_center's fault
directly. It looks like a bad input value is being passed to
poly_center and then to pg_detoast_datum. I'm wondering whether
the bad value is a NULL ... if so, your mistake is not to have
marked the CREATE FUNCTION command "isStrict". The internally-defined
functions you've copied are all marked strict so that they don't
have to think about null inputs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre-Yves LANDURE | 2002-08-08 07:25:50 | Re: Polygon contrib |
| Previous Message | Pierre-Yves LANDURE | 2002-08-08 07:02:28 | Re: Polygon contrib |