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 EAA41811; Thu, 3 Feb 2000 04:17:43 -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 UAA28874; Thu, 3 Feb 2000 20:17:13 +1100 Sender: chris@tech.com.au Message-ID: <38994796.36079744@bitmead.com> Date: Thu, 03 Feb 2000 20:17:10 +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: Tom Lane CC: pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL References: <3898DA32.793A98BA@nimrod.itg.telecom.com.au> <24649.949546519@sss.pgh.pa.us> <3898F8DE.8159BFE7@nimrod.itg.telecom.com.au> <26715.949561209@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Tom Lane wrote: > I'll comment on the other issues later ... but I will say that I don't > think it's acceptable to add *any* overhead to standard-SQL queries > in order to support inheritance better. The vast majority of our users > want SQL performance and don't give a damn about inheritance. We have > to pay attention to that. Well I see that pg_class has columns like "relhasindex". If we added a "relhassubclass", the overhead should be unmeasureable.