Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bGUj0-0001tj-4l for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Jun 2016 17:17:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bGUiz-0001OZ-JI for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Jun 2016 17:17:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bGUhc-0008Ge-JV for pgsql-hackers@postgresql.org; Fri, 24 Jun 2016 17:15:36 +0000 Received: from lists.commandprompt.com ([69.168.55.30]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bGUhZ-0006mI-8P for pgsql-hackers@postgresql.org; Fri, 24 Jun 2016 17:15:34 +0000 Received: from [192.168.1.60] (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id 3101B624; Fri, 24 Jun 2016 10:15:31 -0700 (PDT) Received: from c-73-225-27-179.hsd1.wa.comcast.net ([73.225.27.179] helo=[192.168.1.60]) by assp.commandprompt.com with SMTPSA(TLSv1_2 ECDHE-RSA-AES128-GCM-SHA256) (2.4.5); 24 Jun 2016 10:15:30 -0700 Subject: Re: Bug in to_timestamp(). To: Steve Crawford , Alex Ignatov References: <1873520224.1784572.1465833145330.JavaMail.yahoo.ref@mail.yahoo.com> <1873520224.1784572.1465833145330.JavaMail.yahoo@mail.yahoo.com> <20932.1465834344@sss.pgh.pa.us> <11349.1466429771@sss.pgh.pa.us> Cc: Albe Laurenz , Tom Lane *EXTERN* , Robert Haas , amul sul , PostgreSQL-development From: "Joshua D. Drake" Organization: Command Prompt, Inc. Message-ID: <576D6AB2.5060507@commandprompt.com> Date: Fri, 24 Jun 2016 10:15:30 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Assp-Version: 2.4.5(15162) on assp.commandprompt.com X-Assp-ID: assp.commandprompt.com m1-88531-00036 X-Assp-Session: 7F03FBFAB248 (mail 1) X-Assp-Envelope-From: jd@commandprompt.com X-Assp-Intended-For: pgsql-hackers@postgresql.org X-Assp-Intended-For: sul_amul@yahoo.co.in X-Assp-Intended-For: robertmhaas@gmail.com X-Assp-Intended-For: tgl@sss.pgh.pa.us X-Assp-Intended-For: laurenz.albe@wien.gv.at X-Assp-Intended-For: a.ignatov@postgrespro.ru X-Assp-Intended-For: scrawford@pinpointresearch.com X-Assp-Original-Subject: Re: [HACKERS] Bug in to_timestamp(). X-Assp-Client-SSL: yes X-Pg-Spam-Score: -3.3 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 06/24/2016 09:26 AM, Steve Crawford wrote: > My observation has been that the PostgreSQL development group aims for > correctness and the elimination of surprising results. This was part of > the reason to eliminate a number of automatic casts to dates in earlier > versions. > > To me, 2016-02-30 is an invalid date that should generate an error. > Automatically and silently changing it to be 2016-03-01 strikes me as a > behavior I'd expect from a certain other open-source database, not > PostgreSQL. I don't think anybody could argue with that in good faith. Sincerely, JD -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. Everyone appreciates your honesty, until you are honest with them. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers