Re: backend reset of database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Geoffrey <esoteric(at)3times25(dot)net>, pgsql-general(at)postgresql(dot)org, Terry Lee Tucker <terry(at)leetuckert(dot)net>, John Allgood <john(at)turbocorp(dot)com>, "j(dot) >> \"J(dot) D(dot) Pearson\"" <jpearson(at)turbocorp(dot)com>
Subject: Re: backend reset of database
Date: 2007-04-09 18:31:20
Message-ID: 9106.1176143480@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Geoffrey wrote:
>> CREATE OR REPLACE FUNCTION pcm_getmiles_s(text,text,integer)
>> RETURNS float8 AS '/esc/pgrnd/prog/libpcmiler'
>> LANGUAGE 'c' WITH (isStrict);

> Is this function actually a PostgreSQL callable function? Or is it just
> a general C function along the line of
> float pcm_getmiles_s(char*, char*, int)
> ?

The code would never have worked at all if that were the case (since
text* is not like char*). I suspect some subtler portability issue in
Geoffrey's glue functions. It seems unlikely that moving from PG 7.4.13
to 7.4.16 would in itself have exposed such a problem, but the update in
operating environment from RHEL3 to RHEL4 might've.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Magnus Hagander 2007-04-09 18:32:31 Re: backend reset of database
Previous Message Magnus Hagander 2007-04-09 18:26:30 Re: backend reset of database