| 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>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: 10.1: hash index size exploding on vacuum full analyze |
| Date: | 2017-12-16 03:11:28 |
| Message-ID: | CAA4eK1J93NYL4dDzTjaeJ8WK_D3VByO93S8n+OLCygTq2fg1AQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Nov 23, 2017 at 11:01 AM, AP <pgsql(at)inml(dot)weebeastie(dot)net> wrote:
> On Tue, Nov 21, 2017 at 05:22:18PM +0530, Amit Kapila wrote:
>> I think if we update the stats in copy_heap_data after copying the
>> data, then we don't see such problem. Attached patch should fix the
>> issue. You can try this patch to see if it fixes the issue for you.
>> You might want to wait for a day or so to see if anyone else has any
>> opinion on the patch or my analysis.
>
> I'd love to but I wont be able to now for a week or two.
>
Can you try to verify the patch, if you have some bandwidth now?
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-12-16 03:38:23 | Re: 10.1: hash index size exploding on vacuum full analyze |
| Previous Message | Amit Kapila | 2017-12-16 03:04:34 | Re: 10.1: hash index size exploding on vacuum full analyze |