Date: Fri, 28 Feb 2020 02:23:25 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Message-ID: <1582881805129-0.post@n3.nabble.com>
In-Reply-To: <20200228162914.b296b29eefa23d28d3048d98@sraoss.co.jp>
References: <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>
 <1577490124579-0.post@n3.nabble.com> <1582839355247-0.post@n3.nabble.com>
 <20200228162914.b296b29eefa23d28d3048d98@sraoss.co.jp>
Subject: Re: Implementing Incremental View Maintenance
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

>> thank you for patch v14, that fix problems inherited from temporary
tables.
>> it seems that this ASSERT problem with pgss patch is still present ;o(
>> 
>
> Sorry but we are busy on fixing and improving IVM patches. I think fixing
> the assertion failure needs non trivial changes to other part of
> PosthreSQL.
> So we would like to work on the issue you reported after the pgss patch
> gets committed.

Imagine it will happen tomorrow !
You may say I'm a dreamer
But I'm not the only one
...
...


--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html