Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iehcO-00053S-IF for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Dec 2019 15:40:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iehcN-0002Ib-34 for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Dec 2019 15:40:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iehcM-0002IU-RU for pgsql-bugs@lists.postgresql.org; Tue, 10 Dec 2019 15:40:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iehcK-0008Go-D2 for pgsql-bugs@lists.postgresql.org; Tue, 10 Dec 2019 15:40:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xBAFdxf3006509; Tue, 10 Dec 2019 10:39:59 -0500 From: Tom Lane To: "David G. Johnston" cc: pjander2@gmail.com, PostgreSQL mailing lists Subject: Re: BUG #16158: Check constraints using SQL functions work incorrectly In-reply-to: References: <16158-7ccf2f74b3d655db@postgresql.org> Comments: In-reply-to "David G. Johnston" message dated "Tue, 10 Dec 2019 08:00:24 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6507.1575992399.1@sss.pgh.pa.us> Date: Tue, 10 Dec 2019 10:39:59 -0500 Message-ID: <6508.1575992399@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "David G. Johnston" writes: > You should read the most current version of the documentation for a feature > before reporting a bug. In this case the warnings you desired have been > added to more recently versions of the documentation. Hm, I was thinking that that text had been there for awhile --- certainly it's not a new restriction. I wonder why we didn't back-patch it? regards, tom lane