Date: Sun, 22 Dec 2019 13:22:50 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Message-ID: <1577046170225-0.post@n3.nabble.com>
In-Reply-To: <20191220140232.57b43c4f6296f793d42946b2@sraoss.co.jp>
References: <20191128171052.ee3948fad09eb9337fcbbfc9@sraoss.co.jp>
 <20191129.071944.530831741282571640.t-ishii@sraoss.co.jp>
 <20191129130053.b2cdf2303ff35e437dd39571@sraoss.co.jp>
 <CA+HiwqFHvD5ZuewZ+srr+er6yoZu9tD_Pdjxu8G2vBvKPyQe=Q@mail.gmail.com>
 <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>
Subject: Re: Implementing Incremental View Maintenance
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hello,

First of all many thanks for this Great feature 
replacing so many triggers by a so simple syntax ;o)

I was wondering about performances and add a look 
at pg_stat_statements (with track=all) with IVM_v9.patch.

For each insert into a base table there are 3 statements:
- ANALYZE pg_temp_3.pg_temp_81976
- WITH updt AS (  UPDATE public.mv1 AS mv SET __ivm_count__ = ...
- DROP TABLE pg_temp_3.pg_temp_81976

It generates a lot of lines in pg_stat_statements with calls = 1.
Thoses statements can not be shared because the temp table is dropped each
time.

Is there a plan to change this ?

Many Thanks again

Regards
PAscal


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