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 1i8kEr-0005ly-T2 for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Sep 2019 11:59:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i8kEo-0004qd-CZ for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Sep 2019 11:59:42 +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 1i8kEo-0004qU-4t for pgsql-bugs@lists.postgresql.org; Fri, 13 Sep 2019 11:59:42 +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 1i8kEf-0001qv-Dh for pgsql-bugs@lists.postgresql.org; Fri, 13 Sep 2019 11:59:40 +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 x8DBxOni012461; Fri, 13 Sep 2019 07:59:24 -0400 From: Tom Lane To: Vinay Banakar cc: Andres Freund , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg In-reply-to: References: <16006-99290d2e4642cbd5@postgresql.org> <28076.1568320435@sss.pgh.pa.us> <20190912211047.kr7e4pn7iof76jfx@alap3.anarazel.de> <1141.1568327305@sss.pgh.pa.us> <23378.1568348957@sss.pgh.pa.us> Comments: In-reply-to Vinay Banakar message dated "Fri, 13 Sep 2019 14:23:37 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12459.1568375964.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 13 Sep 2019 07:59:24 -0400 Message-ID: <12460.1568375964@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Vinay Banakar writes: > I see > https://github.com/postgres/postgres/commit/7f1f72c44400e6fef3436b05f1ad= 0f6bacd03d96 > is checked in. However, do you suggest I build pg from this master branc= h > for my bench marking (benchmarking pg with a particular > dataset) or should I wait until the next STABLE release is created (if s= o > do you have any information on when the next one will be released)? The next scheduled releases are in November. https://www.postgresql.org/developer/roadmap/ regards, tom lane