Horton
Menu

Re: mat views stats

Jim Nasby <jim.nasby@bluetreble.com>

View thread
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Jim Mlodgenski <jimmy76@gmail.com>
Cc: PgHacker <pgsql-hackers@postgresql.org>
Date: 2017-02-22T15:18:12Z
Lists: pgsql-hackers 
On 2/22/17 7:56 AM, Peter Eisentraut wrote:
> What behavior would we like by default?  Refreshing a materialized view
> is a pretty expensive operation, so I think scheduling an analyze quite
> aggressively right afterwards is often what you want.
>
> I think sending a stats message with the number of inserted rows could
> make sense.

+1 on both counts. And if sane analyze behavior does depend on the stats 
changes then there's no real advantage to a separate patch.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix REFRESH MATERIALIZED VIEW to report activity to the stats collector.