Re: query against pg_locks leads to large memory alloc

From: Dave Owens <dave(at)teamunify(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: query against pg_locks leads to large memory alloc
Date: 2014-08-19 17:50:41
Message-ID: CA+OQrzgZPudu4Rdo6+qFPS2Y-bfXmHCfVuJtfFE-=0NXmZb9mw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I wonder if it would be helpful to restart the database, then begin
gathering information pg_locks while it can still respond to queries.
I speculate that this is possible because the amount of memory needed
to query pg_locks continues to grow (around 1900MB now).

Dave Owens

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2014-08-19 17:55:26 Re: query against pg_locks leads to large memory alloc
Previous Message Dave Owens 2014-08-19 17:25:50 Re: query against pg_locks leads to large memory alloc