Re: Polygon contrib
От | Pierre-Yves LANDURE |
---|---|
Тема | Re: Polygon contrib |
Дата | |
Msg-id | 1028791550.829.13.camel@timbeure обсуждение исходный текст |
Ответ на | Re: Polygon contrib (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-patches |
The used query is : SELECT @@polygon(box '((120,-10),(160,15))') it's a query that use a C code which normally is not bug.. ;) Pierre-Yves Landuré Le jeu 08/08/2002 à 09:20, Tom Lane a écrit : > Pierre-Yves LANDURE <pylandur@ifremer.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
В списке pgsql-patches по дате отправления: