| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Luke Lonergan <llonergan(at)greenplum(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 8.3 / 8.2.6 restore comparison |
| Date: | 2008-02-22 17:54:00 |
| Message-ID: | 6104.1203702840@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> IIRC we were speculating that data was being written
>> in a pattern that required a lot of seeking thus ruining throughput,
>> but we didn't have any hard evidence of that. Did you do the
>> strace'ing I suggested?
> Yes, I asked if you wanted counts or the whole output. You didn't
> answer :). I provided the counts.
Uh, sorry. Counts are useless here, we need to see the sequence of
write locations to find out if there's a lot of nonconsecutive
writes happening. BTW, the strace had better run across the whole
PG process tree --- it's quite possible that there's some interaction
between the bgwriter and the backend doing COPY, for instance.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-02-22 18:04:49 | Re: 8.3 / 8.2.6 restore comparison |
| Previous Message | Richard Huxton | 2008-02-22 17:53:29 | Re: Full-text search default vs specified configuration |