| From: | Matteo Beccati <php(at)beccati(dot)com> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | Sören Meyer-Eppler <soerenme(at)google(dot)com>, pgsql-performance(at)postgresql(dot)org | 
| Subject: | Re: PostgreSQL 9.0.4 blocking in lseek? | 
| Date: | 2011-12-28 18:02:36 | 
| Message-ID: | 4EFB59BC.9000208@beccati.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-performance | 
Hi,
> 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:
> http://explain.depesz.com/s/TqD
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
a behaviour?
Cheers
-- 
Matteo Beccati
Development & Consulting - http://www.beccati.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2011-12-28 18:07:34 | Re: PostgreSQL 9.0.4 blocking in lseek? | 
| Previous Message | Jim Crate | 2011-12-28 17:22:49 | Re: Subquery flattening causing sequential scan |