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-11 23:18:32
Message-ID: 21865.950311112@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:
> and the reason for the SIGSEGV, is that somehow, text_int4(text *string) in
> src/backend/utils/adt/int.c is called with string=(text *)0x0, so obviously
> this is a problem!

Um. Probably you have a NULL value in "tblPerson"."USN" somewhere?

There are a lot of functions without adequate defenses against NULL
inputs :-( --- we've been cleaning them up slowly, but evidently you
found another one.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2000-02-12 10:56:47 Re: [HACKERS] Re: ECPG documentation
Previous Message Hannu Krosing 2000-02-11 21:53:05 Re: AW: AW: [HACKERS] Another nasty cache problem