| From: | AP <pgsql(at)inml(dot)weebeastie(dot)net> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | 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-27 04:40:13 |
| Message-ID: | 20171227044012.5ypisxbefx4otvyj@inml.weebeastie.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Dec 26, 2017 at 07:18:48PM +0300, Teodor Sigaev wrote:
> > 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?
I shall. I think (hope - grr) the last on-fire issue has been squished* so
things are looking good for me to poke this next week.
Andrew.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2017-12-27 15:29:18 | Re: 10.1: hash index size exploding on vacuum full analyze |
| Previous Message | Amit Kapila | 2017-12-27 04:13:55 | Re: 10.1: hash index size exploding on vacuum full analyze |