From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | phd2(at)earthling(dot)net |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] sorting big tables :( |
Date: | 1998-05-21 11:47:13 |
Message-ID: | Pine.BSF.3.96.980521074402.134A-100000@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 21 May 1998, Oleg Broytmann wrote:
> Hello!
>
> On Wed, 20 May 1998, The Hermit Hacker wrote:
> > > No, that doesn't happen. The only way to eliminate fragmentation is a
> > > dump/newfs/restore cycle. UFS does do fragmentation avoidance (which is
> > > reason UFS filesystems have a 10% reserve).
> >
> > Okay, then we have two different understandings of this. My
> > understanding was that the 10% reserve gave the OS a 'temp area' in which
> > to move blocks to/from so that it could defrag on the fly...
>
> No, you are wrong. This 10% is temp area reserved for emergent
> situations - when root bring system down to single-user and do system
> maintainance.
Actually, in this one you are only partly right. Only root has
*access* to using that extra 10%, but, as I've been corrected by several
ppl, including a couple on the FreeBSD list, that 10% is meant to
*prevent/reduce* fragmentation.
From | Date | Subject | |
---|---|---|---|
Next Message | David Gould | 1998-05-21 18:10:07 | Re: [HACKERS] [QUESTIONS] lo_write cannot > 640Kb? memory leaks? |
Previous Message | Park, Chul-Su | 1998-05-21 09:09:54 | [QUESTIONS] lo_write cannot > 640Kb? memory leaks? |