| From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL win32 fragmentation issue |
| Date: | 2006-12-03 08:56:34 |
| Message-ID: | 65937bea0612030056s2816d005ibac887ef0e8f5dae@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/2/06, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>
> On Sat, 2006-12-02 at 13:34 -0300, Alvaro Herrera wrote:
> > Joshua D. Drake wrote:
> >
> > > My concern is that this is over a single bench run. I could imagine
> that
> > > after a week or two weeks of stead PostgreSQL use, the IO would
> > > gradually get worse and worse.
> >
> > Well, we mostly do random reads (seek) all the time anyway, so is this
> > really a concern?
>
> Wouldn't it be for writes?
Also, huge index range scans can be badly affected by file level
fragmentation.
Regards,
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2006-12-03 09:03:12 | Re: PostgreSQL win32 fragmentation issue |
| Previous Message | Ken Johanson | 2006-12-03 07:32:45 | Re: [HACKERS] Case Preservation disregarding case |