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 1ixDt9-0004w3-Cv for pgsql-hackers@arkaria.postgresql.org; Thu, 30 Jan 2020 17:45:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ixDt8-0006kW-7i for pgsql-hackers@arkaria.postgresql.org; Thu, 30 Jan 2020 17:45:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ixDt7-0006kO-S6 for pgsql-hackers@lists.postgresql.org; Thu, 30 Jan 2020 17:45:58 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ixDsT-0000Er-Kn for pgsql-hackers@postgresql.org; Thu, 30 Jan 2020 17:45:56 +0000 Received: from hnk.local (p1752128-ipbf1308funabasi.chiba.ocn.ne.jp [123.218.229.128]) by oss.nttdata.com (Postfix) with ESMTPSA id 657A36029A; Fri, 31 Jan 2020 02:45:13 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.101.5 at oss.nttdata.com Subject: Re: table partitioning and access privileges From: Fujii Masao To: Tom Lane Cc: Amit Langote , Fujii Masao , PostgreSQL-development References: <6218.1577388354@sss.pgh.pa.us> <3546b691-b744-12c9-fd2f-7dc31c3c030e@oss.nttdata.com> <21015.1580400165@sss.pgh.pa.us> Message-ID: Date: Fri, 31 Jan 2020 02:45:13 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020/01/31 1:28, Fujii Masao wrote: > > > On 2020/01/31 1:02, Tom Lane wrote: >> Fujii Masao writes: >>> Thanks for updating the patch! Barring any objection, >>> I will commit this fix and backport it to all supported versions. >> >> Sorry for not having paid closer attention to this thread, but ... >> is back-patching this behavioral change really a good idea? >> >> It's not that hard to imagine that somebody is expecting the old >> behavior and will complain that we broke their application's security. >> So I'd have thought it better to fix only in HEAD, with a >> compatibility warning in the v13 release notes. >> >> I'm afraid it's much more likely that people will complain about >> making such a change in a minor release than that they will be >> happy about it.  It's particularly risky to be making it in what >> will be the last 9.4.x release, because we will not have any >> opportunity to undo it in that branch if there is pushback. > > Fair enough. I finally did back-patch because the behavior is clearly > documented and I failed to hear the opinions to object the back-patch. > But I should have heard and discussed such risks more. > > I'm OK to revert all those back-patch. Instead, probably the document > should be updated in old branches. I'm thinking to wait at least half a day before reverting the back-patch just in case someone can give opinion during that period. Regards, -- Fujii Masao NTT DATA CORPORATION Advanced Platform Technology Group Research and Development Headquarters