From: | "Andrej Ricnik-Bay" <andrej(dot)groups(at)gmail(dot)com> |
---|---|
To: | bo(dot)berglund(at)telia(dot)com, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Inserting values into a variable table |
Date: | 2006-11-26 20:39:57 |
Message-ID: | b35603930611261239y9dde713jbc625a3748d6edf4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 11/27/06, Bo Berglund <bo(dot)berglund(at)telia(dot)com> wrote:
> >> I'm not sure if PostGreSQL will handle this better. But my main concern over
> >> this matter is the problem with Disk I/O on one big table.
> >Me neither - I wouldn't think it does make a difference for the better, but
> > to be sure I'd try to bench-mark it, with the same data-volume once in
> >one big table, and once indisparate tables (and see what indexing does
> >in both cases).
> Look out for file fragmentation too!
> If the volume where you store the data does not have a *large* free
> area any big file would be fragmented and the head starts jumping like
> mad.
> Before benchmarking I would shut down the server and then defrag the
> disk.
I wouldn't; my logic tells me that disparate tables will cause MORE
head-movement than a single (well-indexed) table ... and my Linux
file systems a) don't fragment to begin with and b) don't have any
defragmentation tools for that reason. ;}
> Bo Berglund
Cheers,
Andrej
From | Date | Subject | |
---|---|---|---|
Next Message | Bo Berglund | 2006-11-26 21:10:13 | Re: Inserting values into a variable table |
Previous Message | Bo Berglund | 2006-11-26 20:12:10 | Re: Inserting values into a variable table |