X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E6F7DD1B1DA for ; Wed, 30 Jun 2004 01:52:33 -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 28256-04 for ; Wed, 30 Jun 2004 04:52:31 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id DD7F3D1B199 for ; Wed, 30 Jun 2004 01:52:30 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i5U4qQJZ003996; Wed, 30 Jun 2004 00:52:26 -0400 (EDT) To: Joe Conway Cc: Jean-Denis Giguere , pgsql-admin@postgresql.org Subject: Re: grant execute on many functions In-reply-to: <40E24551.3080606@joeconway.com> References: <40E1E1A9.8080207@fastmail.fm> <40E1ECEF.5090007@joeconway.com> <3318.1088567114@sss.pgh.pa.us> <40E23F72.4000108@joeconway.com> <3719.1088569577@sss.pgh.pa.us> <40E24551.3080606@joeconway.com> Comments: In-reply-to Joe Conway message dated "Tue, 29 Jun 2004 21:45:05 -0700" Date: Wed, 30 Jun 2004 00:52:25 -0400 Message-ID: <3995.1088571145@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/391 X-Sequence-Number: 14051 Joe Conway writes: > Tom Lane wrote: >> Um. Sooner or later we ought to do something about the whole >> automatic-casting-to-and-from-text issue. Datatypes shouldn't have to >> supply both I/O procedures and text cast procedures. > I thought automatic (i.e. implicit) casting-to-and-from-text was a no-no > because it could cause strange and unintended conversion to take place, > no? Sorry, I was imprecise. I think that the system should automatically provide a coercion to/from text implemented on top of a datatype's I/O procedures. I do not say that that coercion should be *applied* implicitly --- I'd favor requiring explicit cast syntax to get it. For datatypes that have a close enough affinity to text for implicit coercion behavior to be reasonable, we should expect the datatype designer to create a pg_cast entry to say so. In my mind cleaning up this area needs to tie into rationalizing the current mismash of some-datatypes-have-implicit-coercions-and-some- do-not behaviors. That doubtless involves breaking some existing applications :-( but it would surely make the overall behavior much more predictable. regards, tom lane