Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0NF1dl35283 for ; Wed, 23 Jan 2002 10:01:40 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g0NExef02480; Wed, 23 Jan 2002 09:59:40 -0500 (EST) To: "Henshall, Stuart - WCP" cc: Peter Eisentraut , Fernando Nasser , pgsql-hackers@postgresql.org Subject: Re: RFD: schemas and different kinds of Postgres objects In-reply-to: References: Comments: In-reply-to "Henshall, Stuart - WCP" message dated "Wed, 23 Jan 2002 11:03:16 +0000" Date: Wed, 23 Jan 2002 09:59:39 -0500 Message-ID: <2477.1011797979@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/1040 X-Sequence-Number: 18024 "Henshall, Stuart - WCP" writes: > Could you just have a general rule of search in order of age (by OID)? No, unless you plan to abandon the whole notion of resolving ambiguous operator/function calls. (Which'd cut down our TODO list a good bit ;-) but I don't think users would be happy...) OID/age ordering generally has little to do with reasonable resolution behavior. regards, tom lane