Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA07087; Thu, 3 Feb 2000 02:00:21 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id CAA26718; Thu, 3 Feb 2000 02:00:10 -0500 (EST) To: chris@bitmead.com cc: pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL 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> Comments: In-reply-to Chris Bitmead message dated "Thu, 03 Feb 2000 14:41:18 +1100" Date: Thu, 03 Feb 2000 02:00:09 -0500 Message-ID: <26715.949561209@sss.pgh.pa.us> From: Tom Lane Chris Bitmead 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