| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | wnordmann(at)gmx(dot)de, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #12850: ANALYZE of big table is taking extreemly much memory |
| Date: | 2015-03-12 15:30:22 |
| Message-ID: | 5501B10E.8020408@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 03/11/2015 05:35 PM, wnordmann(at)gmx(dot)de wrote:
> The following bug has been logged on the website:
>
> Bug reference: 12850
> Logged by: walter nordmann
> Email address: wnordmann(at)gmx(dot)de
> PostgreSQL version: 9.4.1
> Operating system: Ubuntu 14.4 LTS
> Description:
>
> Vacuuming a really big table (139.000.000 records, 66GB tablespace, one
> GIN-INDEX of 135 GB!) is consuming extreemly much memory. Much, much more
> then maintenance_work_mem (2GB). at this time about 85 GB of virt mem.
>
> see post "autovacuum worker running amok - and me too" at postgresql-general
> or ask me for more data. this form is to small for it.
To be precise, the memory leak is in VACUUM of GIN indexes, not ANALYZE.
It was introduced by the 9.4 GIN changes to store the posting lists in a
compressed form.
Fixed, thanks for the report!
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2015-03-12 19:11:32 | Re: BUG #12856: No space left on device, but there is space! |
| Previous Message | Alvaro Herrera | 2015-03-12 14:45:33 | Re: pg_upgrade failure on Windows Server |