From: | Sören Meyer-Eppler <soerenme(at)google(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | PostgreSQL 9.0.4 blocking in lseek? |
Date: | 2011-10-26 15:47:08 |
Message-ID: | 4EA82B7C.1040008@google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
We are running into a significant performance issue with
"PostgreSQL 9.0.4 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.4.real
(Debian 4.4.5-8) 4.4.5, 64-bit"
(the version string pqAdmin displays).
A fairly complex insert query on an empty destination table will run for
an indefinite amount of time (we waited literally days for the query to
complete). This does not happen every time we run the query but often.
Now ordinarily I'd assume we did something wrong with our indices or
query, but the execution plan looks sane and, more tellingly, we have:
- no CPU load
- no network traffic
- no disk I/O
- no other load on the server except this single query
and strace displaying a seemingly endless list of lseek calls.
So my assumption is that we are not running into bad Big-O() runtime
behavior but rather into some locking problem.
Any ideas what might cause this? Workarounds we could try?
thank you,
Sören
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-10-26 19:57:22 | Re: Bad plan by Planner (Already resolved?) |
Previous Message | Tom Lane | 2011-10-26 14:45:29 | Re: Anti join miscalculates row number? |