Re: backend reset of database

Tom Lane wrote:
> 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.

This is an interesting point. I might try to see if I can duplicate the
problem on a RH3 box.

We'll take a good hard look at our code to see if we have some sloppy
pointers or string length issues.

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin