Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id C1B119F9F0E for ; Sun, 3 Dec 2006 01:56:16 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 39965-05-5 for ; Sun, 3 Dec 2006 01:56:12 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id E5B4A9F9F47 for ; Sun, 3 Dec 2006 01:55:42 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kB35tcic013345; Sun, 3 Dec 2006 00:55:38 -0500 (EST) To: Ken Johanson cc: Martijn van Oosterhout , pgsql-sql@postgresql.org Subject: Re: [HACKERS] Case Preservation disregarding case In-reply-to: <45725923.7010500@kensystem.com> References: <200610301928.51255.beauh@bluefrogmobile.com> <23177.1162265010@sss.pgh.pa.us> <45712E31.1030004@kensystem.com> <20061202133556.GC26365@svana.org> <457199E4.3010401@kensystem.com> <4571A3AF.6070608@zigo.dhs.org> <4571AE66.7050304@kensystem.com> <4571B392.6020303@zigo.dhs.org> <4571C133.1060200@kensystem.com> <20061202201822.GD26365@svana.org> <45725923.7010500@kensystem.com> Comments: In-reply-to Ken Johanson message dated "Sat, 02 Dec 2006 21:57:07 -0700" Date: Sun, 03 Dec 2006 00:55:38 -0500 Message-ID: <13344.1165125338@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/31 X-Sequence-Number: 26987 Ken Johanson writes: > Martijn van Oosterhout wrote: >> I think it's unlikely to happen anytime soon. The primary reason being >> that then you can no longer use indexes to search the catalog. Which > I take a different opinion on this: > -*If* the option to turn on case-insenetive behavior were selectable at > the DB or session level, the existing apps could continue to use the > case sensitve mode and be completely unaffected. Ken, you clearly fail to understand the point being made above. This is not something that is "selectable at the session level". It won't work from either a functional or performance perspective. The real bottom line, though, is that this community has little respect for proposals that involve moving away from the SQL spec rather than closer to it; and that's what you're asking us to do. The spec is not at all vague about the case-sensitivity of identifiers. Now certainly we are not doing exactly what the spec says, but what you ask is even less like the spec's requirements. regards, tom lane