Received: from qhars001.nortel.com (qhars001.NortelNetworks.com [192.100.101.18]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA65213 for ; Fri, 4 Feb 2000 08:51:19 -0500 (EST) (envelope-from mhh@nortelnetworks.com) Received: from smtprch1.nortel.com (actually erchg0j) by qhars001.nortel.com; Fri, 4 Feb 2000 13:47:38 +0000 Received: from zrchb213.us.nortel.com (actually zrchb213) by smtprch1.nortel.com; Fri, 4 Feb 2000 07:47:22 -0600 Received: from zrtpd003.us.nortel.com ([47.140.224.137]) by zrchb213.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 1F2TKZN8; Fri, 4 Feb 2000 07:47:21 -0600 Received: from americasm01.nt.com (hrtpp28d.us.nortel.com [47.190.110.250]) by zrtpd003.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id DJLAH8Q3; Fri, 4 Feb 2000 08:47:22 -0500 Message-ID: <389AD8E0.83CACDAC@americasm01.nt.com> Date: Fri, 04 Feb 2000 08:49:20 -0500 From: "Mark Hollomon" Reply-To: "Mark Hollomon" Organization: Nortel Networks X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: chris@bitmead.com CC: pgsql-hackers@postgreSQL.org Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL References: <200002030402.XAA03844@candle.pha.pa.us> <38998548.C6C8606A@americasm01.nt.com> <389A04A4.BC343241@nimrod.itg.telecom.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Chris Bitmead wrote: > > Mark Hollomon wrote: > > > > > [ discussion on changing the default to getting subclasses ] > > > > I object. > > Tell me why you object. Performance concerns? Compatibility? Definitely compatibility. The load I see (200 - 300 queries a DAY) isn't enough for me to be concerned about an extra millisecond or two per query. But I certainly understand others concerns in this area. One of my responsibilities at work is the maintenance of a homegrown document indexing and retrieval system. It is about 100K of Perl that calls into a custom Perl wrapper around libpq. The system is an escaped 'proof-of-concept'. I wrote it using inheritance features of Postgres95. The upshot is, that this proposed change would require me to examine almost every line of this system in order to make sure that I put ONLY in just the right spots. Yes, this would be where ever there _isn't_ a '*', but how do I grep for the lack of a asterisk? Since it is a "prototype", The code feels very free to pass around small snippets of SQL, a disembodied FROM clause, a portion of a VALUES clause. I simply would not be allowed the time to do the rewrite necessary to accomodate this change. And if I _did_ have the time, I would probably rewrite it for Oracle because then DB Admin would be someone _else's_ job. Now, one of the days, I will find a good excuse (eg new feature) to do a complete rewrite. And _then_ your proposal will actually be a help. And that is why I suggest a SET variable. When I'm ready to use the new feature, I can. But no work is necessary until that day arrives. Thanks for listening. -- Mark Hollomon mhh@nortelnetworks.com ESN 451-9008 (302)454-9008