| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PHP and PostgreSQL |
| Date: | 2001-01-02 04:59:56 |
| Message-ID: | 11150.978411596@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> Now what happens is if someone browses the phorums for a little while, and
> then switches to pages that use our own db classes, you get random slowdowns
> (ie. a select occurs, and then times out after 2 mins or so).
> If you use psql, and perform the select you get a 'shared memory corruption'
> and 'timed out waiting for lock' errors.
Ugh. We would like to think that client misbehavior couldn't cause such
things. Can you dig into this some more, and provide further details on
what is happening and what the sequence of client requests is?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-01-02 05:16:12 | Re: Current Sources/UW7.1.1 |
| Previous Message | Patrick Dunford | 2001-01-02 04:14:02 | Ignored PostgreSQL SET command |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-01-02 07:16:53 | Re: [INTERFACES] Re: PHP and PostgreSQL |
| Previous Message | Rod Taylor | 2001-01-02 04:08:16 | Re: PHP and PostgreSQL |