Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cswFt-0007f8-V8 for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Mar 2017 18:54:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cswFt-0001KP-Hq for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Mar 2017 18:54:09 +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 1cswFs-0001GP-6j for pgsql-hackers@postgresql.org; Tue, 28 Mar 2017 18:54:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cswFp-0005yF-L5 for pgsql-hackers@postgresql.org; Tue, 28 Mar 2017 18:54: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 v2SIs3aZ019434; Tue, 28 Mar 2017 14:54:03 -0400 From: Tom Lane To: Andres Freund cc: pgsql-hackers@postgresql.org Subject: Re: Protection lost in expression eval changeover In-reply-to: <20170328185104.yxs2ewbmb5wl4la7@alap3.anarazel.de> References: <16803.1490723570@sss.pgh.pa.us> <20170328181324.e47nypa4vqg3dpk4@alap3.anarazel.de> <19025.1490726618@sss.pgh.pa.us> <20170328185104.yxs2ewbmb5wl4la7@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 28 Mar 2017 11:51:04 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19432.1490727242.1@sss.pgh.pa.us> Date: Tue, 28 Mar 2017 14:54:02 -0400 Message-ID: <19433.1490727242@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Andres Freund writes: > On 2017-03-28 14:43:38 -0400, Tom Lane wrote: >> I don't see a strong reason why we need to allow a dropped column to go >> to null while we throw an immediate error for a change in column type. >> (If there is some reason, hopefully beta testing will find it.) > Ok. You're doing that? Yeah, I'll go do that. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers