Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0250ZL31001 for ; Tue, 2 Jan 2001 00:00:35 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f024xuC11153; Mon, 1 Jan 2001 23:59:56 -0500 (EST) To: "Christopher Kings-Lynne" cc: pgsql-hackers@postgresql.org Subject: Re: PHP and PostgreSQL In-reply-to: References: Comments: In-reply-to "Christopher Kings-Lynne" message dated "Tue, 02 Jan 2001 11:59:45 +0800" Date: Mon, 01 Jan 2001 23:59:56 -0500 Message-ID: <11150.978411596@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/15 X-Sequence-Number: 2687 "Christopher Kings-Lynne" 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