| From: | Matthew <matt(at)ctlno(dot)com> |
|---|---|
| To: | "'Gunnar R|nning'" <gunnar(at)candleweb(dot)no>, Nikolay Mijaylov <pg(at)nmmm(dot)nu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | RE: FW: URGENT: pgsql on the web server - memory proble ms.... |
| Date: | 2000-10-05 14:13:43 |
| Message-ID: | 183FA749499ED311B6550000F87E206C0C939F@srv.ctlno.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yes, it sounds like a persistent connection problem with PHP. I know they
help with load speed of postgres, but we have had problems with them.
> -----Original Message-----
> From: Gunnar R|nning [SMTP:gunnar(at)candleweb(dot)no]
> Sent: Thursday, October 05, 2000 8:35 AM
> To: Nikolay Mijaylov
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] FW: URGENT: pgsql on the web server - memory
> problems....
>
> "Nikolay Mijaylov" <pg(at)nmmm(dot)nu> writes:
>
> > The problem is that PHP is auto killing after a while (1-2 min), but the
> pos
> > tgres backend process stay (and works about 2 or many more hours). Soon
> all
> > Linux is filled with 64 postgres processes, free memory is 0 and Linux,
> free
> > ze :)
> >
>
> The postgres backend processes should die when the connections are
> closed. Are you sure that the process that runs PHP doesn't keep the
> connections open ? You should check open ports using netstat -a and maybe
> go on using lsof to check the client processes.
>
> regards,
>
> Gunnar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-05 14:32:35 | Re: [SQL] Object syntax |
| Previous Message | Nikolay Mijaylov | 2000-10-05 13:59:51 | RE: FW: URGENT: pgsql on the web server - memory problems.... |