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 HAA95161; Thu, 3 Feb 2000 07:20:37 -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 HAA20081; Thu, 3 Feb 2000 07:09:18 -0500 (EST) From: Bruce Momjian Message-Id: <200002031209.HAA20081@candle.pha.pa.us> Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL In-Reply-To: <38991B2B.939F93CC@nimrod.itg.telecom.com.au> from Chris Bitmead at "Feb 3, 2000 05:07:40 pm" To: chris@bitmead.com Date: Thu, 3 Feb 2000 07:09:18 -0500 (EST) CC: Don Baccus , 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 > Don Baccus wrote: > > > > At 09:55 PM 2/2/00 -0500, Tom Lane wrote: > > > > >There is also a nontrivial performance penalty that would be paid > > >for reversing this default, because then every ordinary SQL query > > >would suffer the overhead of looking to see whether there are > > >child tables for each table named in the query. That *really* > > >doesn't strike me as a good idea. > > > > Thank you for pointing this out, because my first reaction to > > the proposal was "what's the overhead for SQL users"? > > > I just did a performance check on this. I found that the overhead > is one tenth of a millisecond on a Sun desktop workstation. Pretty > trivial, and I'm sure it can be improved. Good point. Has to be non-mearurable performance penalty because most people don't use it. Maybe you will need a system cache entry for this. -- 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