> A rather long import process is stuck since ~12hrs on a query that
> normally returns in a few seconds or minutes. Kust like to OP there's
> almost no activity on the box, only a single postgres process at 100% CPU.
> Two separate queries, (although similar) have triggered the issue, and
> they are run one after another. Also, the import is also not always
> failing, I think it happened twice in about 10 runs. We're expected to
> go live in about two weeks so these were only test runs.
> The explain looks like this:
The query eventually completed in more than 18h. For comparison a normal
run doesn't take more than 1m for that specific step.
Do you think that bad stats and suboptimal plan alone could explain such
Development & Consulting - http://www.beccati.com/
In response to
pgsql-performance by date
|Next:||From: Claudio Freire||Date: 2011-12-28 18:07:34|
|Subject: Re: PostgreSQL 9.0.4 blocking in lseek?|
|Previous:||From: Jim Crate||Date: 2011-12-28 17:22:49|
|Subject: Re: Subquery flattening causing sequential scan |