[EMAIL PROTECTED] (Robert E. Bruccoleri) writes:
> With two processors running the same query, it appears to be a
> slowdown. When I look at the system calls, the backends were
> executing about one read per second. With six processors running the
> same query, it appeared to be a deadlock -- no
Dear Tom,
>
>
> [EMAIL PROTECTED] writes:
> > Apparent deadlock for simultaneous sequential scans
>
> > However, if more than one application is run at once, the performance
> > deteriotates drastically.
>
> So is it a deadlock, or a slowdown? How many is "more than one"?
With two processors
[EMAIL PROTECTED] writes:
> Apparent deadlock for simultaneous sequential scans
> However, if more than one application is run at once, the performance
> deteriotates drastically.
So is it a deadlock, or a slowdown? How many is "more than one"?
regards, tom lane
--
Robert Bruccoleri ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Apparent deadlock for simultaneous sequential scans
Long Description
On an SGI Origin 2000 with 32 CPU's, I'm running Postgresql 7.1beta4
using 32768 buffers. I
