pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: chris@bitmead.com
Cc: Don Baccus <dhogaza@pacifier.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Date: Thu, 3 Feb 2000 07:09:18 -0500 (EST)
Message-ID: <200002031209.HAA20081@candle.pha.pa.us> (raw)
In-Reply-To: <38991B2B.939F93CC@nimrod.itg.telecom.com.au>

> 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



view thread (68+ messages)  latest in thread

Message-ID: <200002031209.HAA20081@candle.pha.pa.us>
Permalink:  ../200002031209.HAA20081@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200002031209.HAA20081@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: pgman@candle.pha.pa.us, chris@bitmead.com, dhogaza@pacifier.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
  Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
  In-Reply-To: <200002031209.HAA20081@candle.pha.pa.us>
  References: <38991B2B.939F93CC@nimrod.itg.telecom.com.au> <200002031209.HAA20081@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox