| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | AP <pgsql(at)inml(dot)weebeastie(dot)net>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: 10.1: hash index size exploding on vacuum full analyze |
| Date: | 2017-12-26 16:18:48 |
| Message-ID: | c3649406-35f1-c018-1a79-cb519772a699@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> Initially, I have also thought of doing it in swap_relation_files, but
> we don't have stats values there. We might be able to pass it, but
> not sure if there is any need for same. As far as Toast table's case
> is concerned, I don't see the problem because we are copying the data
> row-by-row only for heap where the value of num_tuples and num_pages
> could be different. See copy_heap_data.
Ok, agree. AP (sorry, I don't see your name), could your check that patch fixes
your issue?
Nevertheless, I'm going to push this patch in any case and, suppose, it should
be backpatched to version 10 too, although the bug is not about data loss or any
corruption. But patch looks rather straightforward and has low risk of some new
bugs.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-12-27 04:13:55 | Re: 10.1: hash index size exploding on vacuum full analyze |
| Previous Message | Devrim Gündüz | 2017-12-26 11:38:55 | Re: BUG #14991: postgis-2.4.so: undefined symbol: GEOSMinimumClearance |