Hi Tom,
I am pretty sure that at least for my example there is only ONE
prepared statement created once when the static variable is NULL/Nothing
during the first iteration. Thereafter the same prepared statement is
executed over and over again. As I said it may well be a bug on the ado.net
driver. In any case I will set log_statement = all and will revert with my
findings.
Kind Regards
Yiannis
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Sun 04/12/2011 16:30
To: Ioannis Anagnostopoulos
Cc: pgsql-novice@postgresql.org; ahodgson@simkin.ca
Subject: Re: [NOVICE] Linux server connection process consumes all memory
"Ioannis Anagnostopoulos" <ioannis@anatec.com> writes:
> I am not sure if I can but I will try to attach my server's configuration for
> you to take a look. I am also attaching the vb.net code that is
> executed.
I don't know much of anything about VB, but I am filled with suspicion
that something in the VB infrastructure you're using is not doing what
you think. In particular, I'm betting that repeated executions of this
code are in fact generating new prepared statements without deallocating
old ones. You could investigate that theory by setting log_statement =
all in the server configuration and then watching the server log to see
exactly what SQL commands are actually getting sent.
regards, tom lane
