From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-hackers@postgresql.org
Subject: Re: PHP and PostgreSQL
Date: Mon, 01 Jan 2001 23:59:56 -0500
Message-ID: <11150.978411596@sss.pgh.pa.us> (raw)
In-Reply-To: <NEBBIOAJBMEENKACLNPCKEMHCCAA.chriskl@familyhealth.com.au>
References: <NEBBIOAJBMEENKACLNPCKEMHCCAA.chriskl@familyhealth.com.au>
"Christopher Kings-Lynne" <chriskl@familyhealth.com.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, pgsql-hackers@postgresql.org
Subject: Re: PHP and PostgreSQL
In-Reply-To: <11150.978411596@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox