| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Piotr Foremniak" <piotr(dot)foremniak(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: unstable SELECT performance under load |
| Date: | 2008-12-09 23:25:43 |
| Message-ID: | dcc563d10812091525n66e7fe0bqdb2907c4a92a1494@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Dec 9, 2008 at 3:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Piotr Foremniak <piotr(dot)foremniak(at)gmail(dot)com> writes:
>> When executing some quite complex select queries our 8.3.5 Postgres
>> often hangs. The query that we used to reproduce this problem on our
>> isolated test environment is a quite complex join of ca.15 tables.
>> When executed only once, it always takes ca. 500ms to finish. When
>> executed by a JMeter stress test running a couple of threads
>> simultaneously, ca. 95% of queries also take 500ms to finish. In the
>> remaining 5% cases something weird happens and the same query finishes
>> after several minutes, with the postgres process generating gigabytes
>> of temp files and consuming 100% processor resources.
>
> Hmm, are you *sure* you have geqo = off? Because this sure sounds like
It might have gotten turned on for the user or database so even if
it's set that way in postgresql.conf doesn't mean it's not happening.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-12-09 23:40:45 | Re: Possible bug with ALTER LANGUAGE ... OWNER TO ... |
| Previous Message | Erik Jones | 2008-12-09 23:12:06 | Re: Possible bug with ALTER LANGUAGE ... OWNER TO ... |