Re: strange IS NULL behaviour

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange IS NULL behaviour
Date: 2013-09-07 15:33:28
Message-ID: 20130907153328.GA8617@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Sep 7, 2013 at 10:59:08AM -0400, Bruce Momjian wrote:
> My original problem report was November, 2012:
>
> http://www.postgresql.org/message-id/50B3D11F.20408@2ndQuadrant.com
>
> and my patch to fix this was July 4. Tom gave me a code snipped to test
> PL/pgSQL's handling of record types. I tested that and it looked ok,
> but there are other place to test that I don't know about.

Correction --- my updates to Tom's suggestion was only posted September
4. Anyway, it is on the TODO list now.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-09-07 16:50:59 Re: [PERFORM] encouraging index-only scans
Previous Message Gilles Darold 2013-09-07 15:31:52 Re: review: psql and pset without any arguments