Skip site navigation (1) Skip section navigation (2)

Re: Backend memory growing too much

From: ohp(at)pyrenet(dot)fr
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Backend memory growing too much
Date: 2007-07-21 07:40:31
Message-ID: Pine.UW2.4.53.0707210938350.23089@sun.pyrenet (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi Andrew
On Tue, 17 Jul 2007, Andrew Dunstan wrote:

> Date: Tue, 17 Jul 2007 11:30:43 -0400
> From: Andrew Dunstan <andrew(at)dunslane(dot)net>
> To: ohp(at)pyrenet(dot)fr
> Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
> Subject: Re: [HACKERS] Backend memory growing too much
>
>
>
> ohp(at)pyrenet(dot)fr wrote:
> >
> > I don't know much about DBI/DBD but I know sqlgrey uses a lot of
> > prepare/prepare_cached statements.
> >
> >
>
> You can inhibit DBD::Pg from using server side prepares  if you need to,
> by executing:
>
>   $dbh->{pg_server_prepare} = 0;
>
> (as documented in the excellent DBD::Pg docs).
>
> cheers
>
> andrew
>
Thanks! That made the trick!
I assume this is because sqlgrey prepares statements (always the same) and
neither finish them.

Best regards
-- 
Olivier PRENANT        	        Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges                +33-5-61-50-97-01 (Fax)
31190 AUTERIVE                       +33-6-07-63-80-64 (GSM)
FRANCE                          Email: ohp(at)pyrenet(dot)fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2007-07-21 08:05:01
Subject: Re: Memory leak in vac_update_relstats ?
Previous:From: Andrew - SupernewsDate: 2007-07-21 01:02:20
Subject: Re: Solved? Re: 8.2.4 signal 11 with large transaction

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group