Re: plpython improvements - Mailing list pgsql-patches

From Hannu Krosing
Subject Re: plpython improvements
Date
Msg-id 1146638850.3888.4.camel@localhost.localdomain
Whole thread Raw
In response to Re: plpython improvements  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Ühel kenal päeval, P, 2006-04-30 kell 14:43, kirjutas Tom Lane:
> "Sven Suursoho" <sven@spam.pri.ee> writes:
> > So, what about this in configure:
> > if --with-python && test_iterator_app_crashes
> >    # errcode(FEATURE_NOT_SUPPORTED), errmsg(patch your python)
> >    disable_iterator_feature
> > fi
>
> Testing it in configure is wrong, because there's no guarantee the same
> python library will be used at runtime.

As it is a crash bug, I can see two other ways to test:

1) do the test in startup script (maybe have pg_ctl run something)

2) test it in postmaster by running an external testprogram and see if
it crashes.


How do we handle other buggy library routines, like if some system
library crashes on divide-by-zero or similar ?

----------------
Hannu


pgsql-patches by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Page at a time index scan
Next
From: Simon Riggs
Date:
Subject: Re: Page at a time index scan