pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marten Feldtmann <marten@feki.toppoint.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: chris@bitmead.com
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Date: Thu, 3 Feb 2000 22:19:06 +0100 (CET)
Message-ID: <200002032119.WAA04803@feki.toppoint.de> (raw)
In-Reply-To: <26715.949561209@sss.pgh.pa.us>

> Chris Bitmead <chrisb@nimrod.itg.telstra.com.au> writes:
> 
> 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 said ! 

 Actually I'm a little bit uncertain what ORDBMS really improves ? After
writing a full mapper and wrapper for PostgreSQL and a Smalltalk dialect
I see really no usage for these additional inheritance features databases
like PostgreSQL offer.

 Some points about this:

  - all these additional features are very specific to PostgreSQL and
    are not compatible with other databases. Writing an application 
    based on these features results in non-portable systems.
 
  - Speed is still a very, very important feature for a database. A
    single query, which uses about 5 seconds because the optimizer
    is not very clever to use several indices to improove the 
    query execution is much more worse and can change the structure
    of the whole application program.

  - when creating automatic sql-queries through a mapper one can get
    very complicated sql queries which tests the parser very hard and
    the limits of PostgreSQL has been seen very quickly during
    the development of the wrapper above.

  What I'm missing from these new database are structural changes to
the query system: the possibility to execute complicated 
concatenated queries on the server .. perhaps with different 
parameters.

 Just some ideas about all these nice features

 Marten

 

 





view thread (68+ messages)  latest in thread

Message-ID: <200002032119.WAA04803@feki.toppoint.de>
Permalink:  ../200002032119.WAA04803@feki.toppoint.de/
Also on:    postgresql.org/message-id/200002032119.WAA04803@feki.toppoint.de

 · 

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: marten@feki.toppoint.de, tgl@sss.pgh.pa.us, chris@bitmead.com, pgsql-hackers@postgreSQL.org
  Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
  In-Reply-To: <200002032119.WAA04803@feki.toppoint.de>
  References: <26715.949561209@sss.pgh.pa.us> <200002032119.WAA04803@feki.toppoint.de>

* 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