Received: from mailo.vtcif.telstra.com.au (mailo.vtcif.telstra.com.au [202.12.144.17]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA96021; Thu, 3 Feb 2000 01:10:34 -0500 (EST) (envelope-from chrisb@nimrod.itg.telstra.com.au) Received: (from uucp@localhost) by mailo.vtcif.telstra.com.au (8.8.2/8.6.9) id RAA03437; Thu, 3 Feb 2000 17:10:01 +1100 (EST) Received: from maili.vtcif.telstra.com.au(202.12.142.17) via SMTP by mailo.vtcif.telstra.com.au, id smtpdKtscV_; Thu Feb 3 17:09:40 2000 Received: (from uucp@localhost) by maili.vtcif.telstra.com.au (8.8.2/8.6.9) id RAA27020; Thu, 3 Feb 2000 17:09:38 +1100 (EST) Received: from localhost(127.0.0.1), claiming to be "mail.cdn.telstra.com.au" via SMTP by localhost, id smtpdk5jvm_; Thu Feb 3 17:09:14 2000 Received: from lunitari.nimrod.itg.telecom.com.au (lunitari.nimrod.itg.telecom.com.au [192.53.254.48]) by mail.cdn.telstra.com.au (8.8.2/8.6.9) with ESMTP id RAA10173; Thu, 3 Feb 2000 17:09:10 +1100 (EST) Received: from nimrod.itg.telecom.com.au (majere [192.53.254.45]) by lunitari.nimrod.itg.telecom.com.au (8.9.1/8.9.3) with ESMTP id RAA15417; Thu, 3 Feb 2000 17:08:29 +1100 (EST) Sender: chrisb@nimrod.itg.telstra.com.au Message-ID: <38991B2B.939F93CC@nimrod.itg.telecom.com.au> Date: Thu, 03 Feb 2000 17:07:40 +1100 From: Chris Bitmead Reply-To: chris@bitmead.com Organization: IBM Global Services X-Mailer: Mozilla 4.6 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Don Baccus CC: Tom Lane , chris@bitmead.com, 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> <3898DA32.793A98BA@nimrod.itg.telecom.com.au> <3.0.1.32.20000202210952.0086dd60@mail.pacifier.com> 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.