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 1iji7G-0006d2-BU for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Dec 2019 11:12: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 1iji7C-0003Lw-Nl for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Dec 2019 11:12:38 +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 1iji7C-0003Lp-EV for pgsql-hackers@lists.postgresql.org; Tue, 24 Dec 2019 11:12:38 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1iji76-0002M9-MD for pgsql-hackers@postgresql.org; Tue, 24 Dec 2019 11:12:35 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id E8AEF19A8E044 for ; Tue, 24 Dec 2019 04:12:30 -0700 (MST) Date: Tue, 24 Dec 2019 04:12:30 -0700 (MST) From: legrand legrand To: pgsql-hackers@postgresql.org Message-ID: <1577185950902-0.post@n3.nabble.com> In-Reply-To: <20191224110148.f0bd2967a5cba5b2935405dc@sraoss.co.jp> References: <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> <1577046170225-0.post@n3.nabble.com> <20191223155058.80ab940a318a72d740be59e8@sraoss.co.jp> <1577097678190-0.post@n3.nabble.com> <20191224110148.f0bd2967a5cba5b2935405dc@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 Yugo Nagata wrote > On Mon, 23 Dec 2019 03:41:18 -0700 (MST) > legrand legrand < > legrand_legrand@ > > wrote: > > [ ...] > >> I would even >> prefer a common "table" shared between all sessions like GLOBAL TEMPORARY >> TABLE (or something similar) as described here: >> https://www.postgresql.org/message-id/flat/157703426606.1198.2452090605041230054.pgcf%40coridan.postgresql.org#331e8344bbae904350af161fb43a0aa6 > > Although I have not looked into this thread, this may be help if this is > implemented. However, it would be still necessary to truncate the table > before the view maintenance because such tables always exist and can be > accessed and modified by any users. > > -- > Yugo Nagata < > nagata@.co > > For information, in this table data is PRIVATE to each session, can be purged on the ON COMMIT event and disappear at SESSION end. Yes, this feature could be utile only if it's implemented. And you are rigth some data has to be deleted on the ON STATEMENT event (not sure if TRUNCATE is Global or Session specific in this situation). -- Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html