Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuPmw-0003j3-Vy for pgsql-sql@arkaria.postgresql.org; Wed, 03 Jul 2013 16:20:15 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UuPmw-0008Un-FR for pgsql-sql@arkaria.postgresql.org; Wed, 03 Jul 2013 16:20:14 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuPmv-0008Td-CG for pgsql-sql@postgresql.org; Wed, 03 Jul 2013 16:20:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuPmt-00064k-4N for pgsql-sql@postgresql.org; Wed, 03 Jul 2013 16:20:12 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r63GK6Ee010700; Wed, 3 Jul 2013 12:20:06 -0400 (EDT) From: Tom Lane To: Dev Kumkar cc: Bruce Momjian , Thomas Kellerer , pgsql-sql@postgresql.org Subject: Re: Unquoted column names fold to lower case In-reply-to: References: <1372858894.60580.YahooMailClassic@web161605.mail.bf1.yahoo.com> <20130703152402.GA6492@momjian.us> <20130703153524.GB6492@momjian.us> Comments: In-reply-to Dev Kumkar message dated "Wed, 03 Jul 2013 21:20:54 +0530" Date: Wed, 03 Jul 2013 12:20:06 -0400 Message-ID: <10699.1372868406@sss.pgh.pa.us> X-Pg-Spam-Score: 0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org Dev Kumkar writes: > Any plans to fix this in next release or having a patch to fix this? No. This has been discussed (many times) before. There isn't any feasible way to change this behavior without breaking an incredible amount of code, much of which isn't even under our control. The marginal increase in standards compliance is not worth the pain --- especially when the aspect of the standard in question isn't even one that most of us like. (All-upper-case is hard to read.) If this is a deal-breaker for you, then I'm sorry, but you need to find another database. Postgres settled on this behavior fifteen years ago, and we're not changing it now. regards, tom lane -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql