Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.2/8.9.1) with ESMTP id WAA39045 for ; Sun, 7 Feb 1999 22:48:08 -0500 (EST) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id WAA04656; Sun, 7 Feb 1999 22:48:31 -0500 (EST) From: Bruce Momjian Message-Id: <199902080348.WAA04656@candle.pha.pa.us> Subject: Re: [SQL] Functional Indexes In-Reply-To: <13890.918443915@sss.pgh.pa.us> from Tom Lane at "Feb 7, 1999 10:18:35 pm" To: tgl@sss.pgh.pa.us (Tom Lane) Date: Sun, 7 Feb 1999 22:48:31 -0500 (EST) Cc: marc@fallon.classyad.com, pgsql-sql@hub.org, pgsql-hackers@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > Note to hackers: is there a good reason why indexes are more > restrictive? Offhand it seems like the same physical-equivalence > trick could be applied. What do you mean by restrictive. If you mean: * allow creation of functional indexes to use default types It is on the TODO list, and has been for a while. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026