From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Subject: | Re: tsearch2 problem rank_cd() (possibly) crashing postgres |
Date: | 2006-12-08 16:18:42 |
Message-ID: | 1165594722.24745.4.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, 2006-12-08 at 11:12 -0500, Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > On Fri, 2006-12-08 at 10:47 -0500, Tom Lane wrote:
> >> Nonetheless, dumping core on bad input is not acceptable behavior ...
>
> > Is it time to require test cases for contrib modules?
>
> tsearch2 *has* a regression test. ATM it sounds like the problem is
> that the OP tried to use a new library with old pg_proc entries that
> defined different parameter sets for the same-named C functions; a
> situation that no regression test would have exercised anyway.
Hmmmm, is there a way that we could have library version requirements
for all C based functions? So if within PGLIB version 3 was present but
the function was calling version 2... It would politely fail with a
mismatched version warning?
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-12-08 16:33:04 | Re: Should clients warn in case of server version mismatch |
Previous Message | Tom Lane | 2006-12-08 16:12:54 | Re: tsearch2 problem rank_cd() (possibly) crashing postgres |