| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Pavel Suderevsky <psuderevsky(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14863: wrong reltuples statistics after vacuum without analyze |
| Date: | 2018-04-20 18:36:10 |
| Message-ID: | 20180420183609.GD13438@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg범퍼카 토토SQL : Postg범퍼카 토토SQL 메일 링리스트 : 2018-04-20 이후 PGSQL-BUGS 18:36 |
Hi Pavel
I came across your issue report just now.
Do you know if this is still an issue with the fixes from these commits:
7c91a0364fcf5d739a09cc87e7adb1d4a33ed112
d04900de7d0cb5b6ecb6d5bf9fdb6f3105824f81
BTW it looks like there was a suggestion to backpatch but this wasn't done.
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-04-20 21:57:01 | BUG #15166: PL/PGSQL default rowtype variable value is null but also not null |
| Previous Message | Greg Clough | 2018-04-20 16:51:34 | RE: BUG #15165: The application server could not be contacted |