Re: Not quite a security hole in internal_in

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sergey Burladyan <eshkinkot(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Not quite a security hole in internal_in
Date: 2009-06-10 22:16:32
Message-ID: 15291.1244672192@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Sergey Burladyan <eshkinkot(at)gmail(dot)com> writes:
>> How about contrib/ ? I have this in my test 8.3.7 database:

> That stuff should all be marked strict ... on the whole I'm not sure
> that contrib is null-safe anyway, independently of this particular
> issue. AFAIK no one's really gone through it.

So I just did that, and found one bit of sloppiness in pg_freespacemap,
plus a whole lot of GIST/GIN support functions that aren't marked strict
and probably should be. Will fix. This is actually a lot closer to
being right than I would have bet on before the exercise.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-10 22:21:05 Re: Display of foreign keys in psql
Previous Message Greg Stark 2009-06-10 22:15:47 Re: Display of foreign keys in psql