Re: [HACKERS] Another nasty cache problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: prlw1(at)cam(dot)ac(dot)uk
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Another nasty cache problem
Date: 2000-02-14 16:00:16
Message-ID: 19021.950544016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:

> + if (!string)
> + elog(ERROR, "Trying to convert NULL text to integer (int2)");

This is unreasonable behavior. The correct patch is just

if (!string)
return 0;

which will allow the function manager to plow ahead with returning the
NULL that it's going to return anyway. See the past pghackers threads
about redesigning the function manager interface if you don't understand
what's going on here.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Patrick Welche 2000-02-14 16:14:44 Re: [HACKERS] Another nasty cache problem
Previous Message sszabo 2000-02-14 15:55:14 Limit and Order by stuff