Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id HAA95333; Thu, 3 Feb 2000 07:21:41 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id HAA20196; Thu, 3 Feb 2000 07:13:37 -0500 (EST) From: Bruce Momjian Message-Id: <200002031213.HAA20196@candle.pha.pa.us> Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL In-Reply-To: <38994796.36079744@bitmead.com> from Chris at "Feb 3, 2000 08:17:10 pm" To: Chris Date: Thu, 3 Feb 2000 07:13:36 -0500 (EST) CC: Tom Lane , pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 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. Yes, but how do you keep that accurate? If I add indexes, then drop them, does relhasindex go to false. Could you do that for relhassubclass? -- Bruce Momjian | http://www.op.net/~candle pgman@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