Re: Re: Increased memory utilization by pgsql backend after upgrade from 9.1.3 to 9.2.6

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Dattaram Porob <dattaram(dot)porob(at)gmail(dot)com>
Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Re: Increased memory utilization by pgsql backend after upgrade from 9.1.3 to 9.2.6
Date: 2014-02-05 01:32:46
Message-ID: CAGTBQpacfi+LYBFTZdn9bE0pWBoTTpAt9yV4j2vqm+U2dx4zfg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Jan 30, 2014 at 2:43 PM, Dattaram Porob
<dattaram(dot)porob(at)gmail(dot)com> wrote:
>
> Looks like this memory is being used to cache the query plan. Any ideas, why
> it is occupying such a huge heap in 9.2.6 as compared to 9.1.3 ? I know that
> the same SQL function occupies around 25MB heap in 9.1.3.
>
> Any thoughts/comments?

I believe (not sure) that you can release that memory by issuing a
DISCARD ALL when returning a connection to the pool.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Peter Geoghegan 2014-02-05 02:03:43 Re: Postgres Query Plan Live Lock
Previous Message Jeff Janes 2014-02-05 00:14:51 Re: [PERFORM] encouraging index-only scans