From: | Brian Cox <brian(dot)cox(at)ca(dot)com> |
---|---|
To: | "Craig Ringer [craig(at)postnewspapers(dot)com(dot)au]" <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: query slow; strace output worrisome |
Date: | 2010-04-06 16:24:47 |
Message-ID: | 4BBB604F.6060005@ca.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 04/06/2010 01:18 AM, Craig Ringer [craig(at)postnewspapers(dot)com(dot)au] wrote:
> I'm wondering if the issue is with strace rather than Pg. That is to
> say, that strace is trying to print:
Thanks, Craig: I do think that this is a strace issue.
> As for what Pg is doing: creat() returns -1 on error and a file
> descriptor otherwise, so the return value appears to indicate success.
> I'm kind of wondering what the Pg backend is actually _doing_ though -
> if it was using sort temp files you'd expect
> open()/write()/read()/close() not just creat() calls.
My quesiton exactly: what is the backend doing calling creat() over and
over again? Note that this query does complete -- in 30-40 mins.
Brian
From | Date | Subject | |
---|---|---|---|
Next Message | Ireneusz Pluta | 2010-04-06 16:49:48 | Re: 3ware vs. MegaRAID |
Previous Message | Christiaan Willemsen | 2010-04-06 07:38:54 | Re: Using high speed swap to improve performance? |