Received: from tech.com.au (IDENT:root@techpt.lnk.telstra.net [139.130.75.122]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA11235; Thu, 3 Feb 2000 08:07:46 -0500 (EST) (envelope-from chris@bitmead.com) Received: from bitmead.com (tardis [203.41.180.243]) by tech.com.au (8.9.3/8.9.3) with ESMTP id AAA31652; Fri, 4 Feb 2000 00:05:33 +1100 Sender: chris@tech.com.au Message-ID: <38997D1C.9F353FED@bitmead.com> Date: Fri, 04 Feb 2000 00:05:32 +1100 From: Chris X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i686) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Momjian CC: Tom Lane , pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL References: <200002031237.HAA21220@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bruce Momjian wrote: > Oops: > test=> drop index i_test; > DROP > test=> select relhasindex from pg_class where relname = 'test'; > relhasindex > ------------- > t > (1 row) > > Let me add that to the TODO list. Why not change that to a relnumindexes as well? Easier to maintain and more useful information. > > >Could you do that for relhassubclass? > > > > If we made it relnumsubclasses and incremented/decremented on > > CREATE/DROP, it seems easy in theory. > > Yes, that would work. Seems hasindex has problems.