BUG #12850: ANALYZE of big table is taking extreemly much memory

Started by wambacherabout 11 years ago2 messagesbugs
Jump to latest
#1wambacher
wnordmann@gmx.de

The following bug has been logged on the website:

Bug reference: 12850
Logged by: walter nordmann
Email address: wnordmann@gmx.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.

regards
walter

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Heikki Linnakangas
heikki.linnakangas@enterprisedb.com
In reply to: wambacher (#1)
Re: BUG #12850: ANALYZE of big table is taking extreemly much memory

On 03/11/2015 05:35 PM, wnordmann@gmx.de wrote:

The following bug has been logged on the website:

Bug reference: 12850
Logged by: walter nordmann
Email address: wnordmann@gmx.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

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs