From: Tom Lane <tgl@sss.pgh.pa.us>
To: chris@bitmead.com
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Date: Thu, 03 Feb 2000 02:00:09 -0500
Message-ID: <26715.949561209@sss.pgh.pa.us> (raw)
In-Reply-To: <3898F8DE.8159BFE7@nimrod.itg.telecom.com.au>
References: <3898DA32.793A98BA@nimrod.itg.telecom.com.au>
<24649.949546519@sss.pgh.pa.us>
<3898F8DE.8159BFE7@nimrod.itg.telecom.com.au>
Chris Bitmead <chrisb@nimrod.itg.telstra.com.au> writes:
> Tom Lane wrote:
>>>> 1) An imaginary field in every tuple that tells you the class it came
>> This is a good idea, but it seems to me that it'd fit into the system
>> traditions better if the pseudo-field gave the OID of the source
>> relation.
> What do you think about having both? I know you can go from one to the
> other by joining with pg_class, but that's too inconvenient, and I can't
> make up my mind which is the better "system tradition" either.
If we can implement it as I sketched before, there's no reason not to
offer both, since either one would create zero overhead for any query
not using the feature.
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.
regards, tom lane
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: tgl@sss.pgh.pa.us, chris@bitmead.com, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
In-Reply-To: <26715.949561209@sss.pgh.pa.us>
References: <3898DA32.793A98BA@nimrod.itg.telecom.com.au> <24649.949546519@sss.pgh.pa.us> <3898F8DE.8159BFE7@nimrod.itg.telecom.com.au> <26715.949561209@sss.pgh.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