| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Sven Suursoho <sven(at)spam(dot)pri(dot)ee>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: plpython improvements |
| Date: | 2006-05-03 06:47:30 |
| Message-ID: | 1146638850.3888.4.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Ühel kenal päeval, P, 2006-04-30 kell 14:43, kirjutas Tom Lane:
> "Sven Suursoho" <sven(at)spam(dot)pri(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2006-05-03 07:28:24 | Re: Page at a time index scan |
| Previous Message | Jim C. Nasby | 2006-05-02 22:49:33 | Re: patch review, please: Autovacuum/Vacuum times via stats. |