| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Felipe de Jesús Molina Bravo <fjmolinabravo(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: query reboot pgsql 9.5.1 |
| Date: | 2016-03-04 22:16:13 |
| Message-ID: | 20160304221613.GA745676@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David G. Johnston wrote:
> To be more clear, you need to run a query that will complete in our
> lifetime (and without an OOM error) with all three of ANALYZE, BUFFERS, and
> TIMING specified for the EXPLAIN.
I think the problem is pretty clear. The plan is sensible yet the
result doesn't seem to be. Why do you think using up all the memory is
a sensible result here?
Jaime Casanova suggested that maybe the @> operator have memory leaks.
Or perhaps the GIN index machinery that's using them.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafal Pietrak | 2016-03-04 22:46:07 | Re: multiple UNIQUE indices for FK |
| Previous Message | David G. Johnston | 2016-03-04 22:11:03 | Re: query reboot pgsql 9.5.1 |