pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org, Oleg Bartunov <oleg@sai.msu.su>
Cc: Teodor Sigaev <teodor@sigaev.ru>
Subject: Re: tsearch2 problem rank_cd() (possibly) crashing postgres
Date: Fri, 08 Dec 2006 08:18:42 -0800
Message-ID: <1165594722.24745.4.camel@localhost.localdomain> (raw)
In-Reply-To: <5964.1165594374@sss.pgh.pa.us>
References: <a97c77030612080255h131f708brb68495740219229a@mail.gmail.com>
	<Pine.LNX.4.64.0612081442320.16338@sn.sai.msu.ru>
	<5485.1165592831@sss.pgh.pa.us>
	<1165593203.12459.81.camel@localhost.localdomain>
	<5964.1165594374@sss.pgh.pa.us>

On Fri, 2006-12-08 at 11:12 -0500, Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.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






view thread (15+ messages)  latest in thread

Message-ID: <1165594722.24745.4.camel@localhost.localdomain>
Permalink:  ../1165594722.24745.4.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1165594722.24745.4.camel@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, tgl@sss.pgh.pa.us, oleg@sai.msu.su, teodor@sigaev.ru
  Subject: Re: tsearch2 problem rank_cd() (possibly) crashing postgres
  In-Reply-To: <1165594722.24745.4.camel@localhost.localdomain>
  References: <a97c77030612080255h131f708brb68495740219229a@mail.gmail.com> <Pine.LNX.4.64.0612081442320.16338@sn.sai.msu.ru> <5485.1165592831@sss.pgh.pa.us> <1165593203.12459.81.camel@localhost.localdomain> <5964.1165594374@sss.pgh.pa.us> <1165594722.24745.4.camel@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox