From: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | memory leak in GIN |
Date: | 2016-03-12 07:40:53 |
Message-ID: | CAJGNTeMR1ndMU2Thpr8GPDUfiHTV7idELJRFusA5UXUGY1y-eA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On the spanish list, Felipe de Jesús Molina Bravo, reported a few days
back that a query that worked well in 9.4 consume all memory in 9.5.
With the self contained test he provided us i reproduced the problem
in 9.5 and 9.6dev.
To test, execute:
pba.sql -- to create the tables and populate
query_crash.sql -- this will consume all your memory and crash your
server eventually
If you drop the GIN indexes, the problem disappear.
I used valgrind to try to hunt the memory leak, attached the resulting
log showing the backend that executed the query. And from the little a
could say from the stack trace valgrind showed, the problem is around
ginPostingListDecodeAllSegments() but i don't see any modifications
there.
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
valgrind_pg_4812.log | text/x-log | 9.9 KB |
pba.sql.gz | application/x-gzip | 1.6 MB |
query_crash.sql | application/sql | 407 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2016-03-12 07:52:14 | Re: eXtensible Transaction Manager API (v2) |
Previous Message | Amit Kapila | 2016-03-12 07:24:15 | Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity. |