Re: Single-file DBs WAS: Need concrete "Why Postgres - Mailing list pgsql-hackers

From Jeff
Subject Re: Single-file DBs WAS: Need concrete "Why Postgres
Date
Msg-id Pine.BSF.4.44.0308230927250.5470-100000@torgo.978.org
Whole thread Raw
In response to Re: Single-file DBs WAS: Need concrete "Why Postgres  (Mike Mascari <mascarm@mascari.com>)
Responses Re: Single-file DBs WAS: Need concrete 'Why Postgres
List pgsql-hackers
On Fri, 22 Aug 2003, Mike Mascari wrote:

> In addition to Jan's points, using a single pre-allocated file also
> reduces file descriptor consumption, although I don't know what the
> costs are regarding maintaining the LRU of file descriptors, the price
> of opens and closes, the price of having a high upper limit of file
> descriptors, etc.
>

another thought I had - I wonder how much fragmentation affects postgres
(and others).  On Informix when you use "cooked files" it needs to
preallocate all the space.  I figured part of it was to 1. make the file
seem more like a device 2. reduce fragmentation 3. guarantee that 2GB
"chunk" can never have an out of space issue.

On a dedicated pg box there is probably not much fragmentation (and thanks
to today's modern filesystems, it isn'ttoo big of a deal in any case)..
but it would still be interesting to have numbers..

--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/




pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Collation rules and multi-lingual databases
Next
From: "Andrew Dunstan"
Date:
Subject: Re: Single-file DBs WAS: Need concrete 'Why Postgres