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 1isYt7-00016H-5c for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Jan 2020 21:10:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1isYt5-0002c7-15 for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Jan 2020 21:10:39 +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 1isYt4-0002VL-Ni for pgsql-hackers@lists.postgresql.org; Fri, 17 Jan 2020 21:10:38 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1isYt1-0002OB-3L for pgsql-hackers@postgresql.org; Fri, 17 Jan 2020 21:10:38 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id CF5301A441187 for ; Fri, 17 Jan 2020 14:10:32 -0700 (MST) Date: Fri, 17 Jan 2020 14:10:32 -0700 (MST) From: legrand legrand To: pgsql-hackers@postgresql.org Message-ID: <1579295432714-0.post@n3.nabble.com> In-Reply-To: <20191226110302.6e85967388aea26292dde1b5@sraoss.co.jp> References: <20191129.071944.530831741282571640.t-ishii@sraoss.co.jp> <20191129130053.b2cdf2303ff35e437dd39571@sraoss.co.jp> <20191129181600.7b5dd4167e1753536af33937@sraoss.co.jp> <20191129181954.208da0d63c1ff9e556008e80@sraoss.co.jp> <20191201025514.GY2355@paquier.xyz> <20191202.100118.1160224336488931090.t-ishii@sraoss.co.jp> <20191202110538.a6ff2cd84f488f42eab621eb@sraoss.co.jp> <20191220140232.57b43c4f6296f793d42946b2@sraoss.co.jp> <20191226110302.6e85967388aea26292dde1b5@sraoss.co.jp> Subject: Re: Implementing Incremental View Maintenance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello, It seems that patch v11 doesn't apply any more. Problem with "scanRTEForColumn" maybe because of change: https://git.postgresql.org/pg/commitdiff/b541e9accb28c90656388a3f827ca3a68dd2a308 Regards PAscal -- Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html