From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | AP <pgsql(at)inml(dot)weebeastie(dot)net>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: 10.1: hash index size exploding on vacuum full analyze |
Date: | 2017-12-16 07:26:24 |
Message-ID: | CAA4eK1L1MAOW1yxOg65tRYbBPV0NYwQuYt8bRPy0QANa7c=A4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sat, Dec 16, 2017 at 12:27 PM, AP <pgsql(at)inml(dot)weebeastie(dot)net> wrote:
> On Sat, Dec 16, 2017 at 09:08:23AM +0530, Amit Kapila wrote:
>> On Fri, Dec 15, 2017 at 8:08 PM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
>> The estimation depends on the type of columns and stats. I think we
>> need to use schema and stats in the way AP is using to see the effect
>> AP is seeing. I was under impression that AP will help us in
>> verifying the problem as he can reproduce it, but it seems he is busy.
>
> Different fires keep springing up and they are causing delay. This
> is still on my mind and I'll get back to it as soon as I can.
>
Okay. I think Ashutosh has reproduced it with a standalone test, let
us see if that suffice the need. In any case, feel free to verify in
the meantime.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-12-17 01:40:24 | Re: PostgreSQL crashes with SIGSEGV |
Previous Message | AP | 2017-12-16 06:57:29 | Re: 10.1: hash index size exploding on vacuum full analyze |