Re: mat views stats
Jim Mlodgenski <jimmy76@gmail.com>
From: Jim Mlodgenski <jimmy76@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael.paquier@gmail.com>,
Robert Haas <robertmhaas@gmail.com>, Jim Nasby <Jim.Nasby@bluetreble.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
PgHacker <pgsql-hackers@postgresql.org>
Date: 2017-03-19T13:44:24Z
Lists: pgsql-hackers
> > > But that seems pretty ugly. Given the lack of previous reports, I'm > personally content to leave this unfixed in the back branches. > > Comments? > > Most instances of this I've seen out in the field have worked around this by just running analyze in the scheduled jobs after the refresh so we're probably good not back patching.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix REFRESH MATERIALIZED VIEW to report activity to the stats collector.
- 17f8ffa1e331 10.0 landed