| From: | Jim Mlodgenski <jimmy76(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: mat views stats |
| Date: | 2017-03-19 13:44:24 |
| Message-ID: | CAB_5SReeEsbd24gou25-5CLmF4aQaSs8ecFC9kYWuo=jLxgPEw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2017-03-19 14:12:53 | Re: Logical decoding on standby |
| Previous Message | Petr Jelinek | 2017-03-19 13:30:28 | Re: PoC plpgsql - possibility to force custom or generic plan |