Re: [HACKERS] Backend memory growing too much

2007-07-21 Thread ohp
Hi Andrew On Tue, 17 Jul 2007, Andrew Dunstan wrote: Date: Tue, 17 Jul 2007 11:30:43 -0400 From: Andrew Dunstan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: pgsql-hackers list pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Backend memory growing too much [EMAIL PROTECTED] wrote

[HACKERS] Backend memory growing too much

2007-07-17 Thread ohp
Hi everyone, I've been using sqlgrey for some time now and I'm very surprised by the memory taken by the backends to which sqlgrey is connected. look at process 4111 and 28108 . They roughly take twice the space the other backend take. Could there be a memory leak? I don't know much about

Re: [HACKERS] Backend memory growing too much

2007-07-17 Thread Tom Lane
[EMAIL PROTECTED] writes: I don't know much about DBI/DBD but I know sqlgrey uses a lot of prepare/prepare_cached statements. Well, those aren't exactly free. Possibly you could learn something about it by attaching to one of these backends with gdb and executing call

Re: [HACKERS] Backend memory growing too much

2007-07-17 Thread Andrew Dunstan
[EMAIL PROTECTED] 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