| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Jim Mlodgenski <jimmy76(at)gmail(dot)com> |
| Cc: | PgHacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: mat views stats |
| Date: | 2017-02-22 15:18:12 |
| Message-ID: | b1dac1f3-d168-29cb-059f-ae1b0d0c8b2e@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2017-02-22 15:20:33 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | David G. Johnston | 2017-02-22 15:17:20 | Re: Make subquery alias optional in FROM clause |