X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AD9AE529A0 for ; Tue, 19 Jul 2005 12:01:36 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 52167-01 for ; Tue, 19 Jul 2005 15:01:27 +0000 (GMT) Received: from mfront8.yandex.ru (mfront8.yandex.ru [213.180.200.39]) by svr1.postgresql.org (Postfix) with ESMTP id AC6E85294D for ; Tue, 19 Jul 2005 12:01:25 -0300 (ADT) Received: from YAMAIL (mfront8.yandex.ru) by mail.yandex.ru id ; Tue, 19 Jul 2005 19:01:05 +0400 Date: Tue, 19 Jul 2005 19:01:05 +0400 (MSD) From: "Ilja Golshtein" Message-Id: <42DD15B1.000004.19702@mfront8.yandex.ru> MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] To: tgl@sss.pgh.pa.us Cc: pgsql-general@postgresql.org Subject: Re: Old question - failed to find conversion function from "unknown" In-Reply-To: <23591.1121782655@sss.pgh.pa.us> Reply-To: ilejn@yandex.ru References: <42DCC1E9.2060300@aeccom.com> <42DCCCCE.000006.04382@mfront8.yandex.ru> <42DCDE07.4020906@archonet.com> <42DCEFEE.000005.12199@mfront8.yandex.ru> <23591.1121782655@sss.pgh.pa.us> X-Source-Ip: 194.190.207.155 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.026 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/772 X-Sequence-Number: 80870 Hello! >>> Well, it would obviously be better if PG could figure out it was safe, >>> but I'm not sure there's a general case where it is. You can see it's OK >>> because you know there's only one row in your SELECT result-set. > >> I think, it's OK because NULL can be compared with anything >> with predictable result and no additional information about >> types is necessary. >> Is it correct vision? > >The backend doesn't really distinguish NULL from 'foo' (or untyped >string literals in general) when making datatype decisions. I think when PG is about to compare object of known type and known value (it is 5 in my example) with object with unknown type but known value or known null flag (it is null in my example) it is high time to return 'false' instead of producing error. As far as I understand, it is not about comparision only, but about any operation. I really believe NULLs are special here. Of course I am a complete stranger and unaware of PostgreSQL internals so what I am saying may contradict with some basical concepts. Looks like it does since according to Tom, PostgreSQL does not treat null literals in special way :( Thanks. -- Best regards Ilja Golshtein