From: Matteo Beccati <php@beccati.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sören Meyer-Eppler <soerenme@google.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL 9.0.4 blocking in lseek?
Date: Wed, 28 Dec 2011 19:02:36 +0100
Message-ID: <4EFB59BC.9000208@beccati.com> (raw)
In-Reply-To: <4EFAE7F6.30603@beccati.com>
References: <4EA82B7C.1040008@google.com>
<9398.1319761978@sss.pgh.pa.us>
<4EFAE7F6.30603@beccati.com>
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/
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-performance@postgresql.org
Cc: php@beccati.com, tgl@sss.pgh.pa.us, soerenme@google.com
Subject: Re: PostgreSQL 9.0.4 blocking in lseek?
In-Reply-To: <4EFB59BC.9000208@beccati.com>
* 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