Re: 10.1: hash index size exploding on vacuum full analyze - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: 10.1: hash index size exploding on vacuum full analyze
Date
Msg-id CAA4eK1L1MAOW1yxOg65tRYbBPV0NYwQuYt8bRPy0QANa7c=A4Q@mail.gmail.com
Whole thread Raw
In response to Re: 10.1: hash index size exploding on vacuum full analyze  (AP <pgsql@inml.weebeastie.net>)
Responses Re: 10.1: hash index size exploding on vacuum full analyze  (Ashutosh Sharma <ashu.coek88@gmail.com>)
List pgsql-bugs
On Sat, Dec 16, 2017 at 12:27 PM, AP <pgsql@inml.weebeastie.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@sigaev.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


pgsql-bugs by date:

Previous
From: AP
Date:
Subject: Re: 10.1: hash index size exploding on vacuum full analyze
Next
From: Peter Geoghegan
Date:
Subject: Re: PostgreSQL crashes with SIGSEGV