Unanswered: Multiple postmaster instances consuming system memory
I am running postgresql 8.0.12. My local application queries the db and I see postmaster fork a new connection. Instead of the connection being handed off to the backend, the postmaster instance remains idle and doesn't time out. Eventually there are dozens of these using up all shared memory.
Does anyone have any insight into what causes this behavior? I have 8GB of RAM and have set 2GB for shared_buffers. Currently, when I start up the db nearly all the system memory is taken within an hour.
I'm still pretty new to postgresql, so any help would be appreciated.
Yeah - the only time I've seen that is when I either fail to properly close/release a connection object in the app I'm developing, or the client app crashes without releasing the connection.
"Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
"I have my standards. They may be low, but I have them!" - Bette Middler
"It's a book about a Spanish guy named Manual. You should read it." - Dilbert