"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
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2001-01-02 05:16:12|
|Subject: Re: Current Sources/UW7.1.1 |
|Previous:||From: Patrick Dunford||Date: 2001-01-02 04:14:02|
|Subject: Ignored PostgreSQL SET command|
pgsql-interfaces by date
|Next:||From: Bruce Momjian||Date: 2001-01-02 07:16:53|
|Subject: Re: [INTERFACES] Re: PHP and PostgreSQL|
|Previous:||From: Rod Taylor||Date: 2001-01-02 04:08:16|
|Subject: Re: PHP and PostgreSQL|