Re: PostgreSQL win32 fragmentation issue
Gurjeet Singh <singh.gurjeet@gmail.com>
From: "Gurjeet Singh" <singh.gurjeet@gmail.com>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Mark Kirkwood" <markir@paradise.net.nz>, "Andrew Dunstan" <andrew@dunslane.net>, "Joshua D. Drake" <jd@commandprompt.com>, "Martijn van Oosterhout" <kleptog@svana.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2006-12-03T09:03:12Z
Lists: pgsql-hackers
On 12/3/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Mark Kirkwood <markir@paradise.net.nz> writes:
> > A related point comes to mind, consider the single "tablespace" file for
> > example: It may have no fragmentation from a *file* perspective, but
> > supposing you have several busy relations being inserted or updated then
> > pages (or groups of pages) for these could be "fragmented" throughout
> > the tablespace file.
>
> +1 ... what was said upthread sounds to me like those other databases
> are just hiding the fragmentation issue within their
> huge-files-you-can't-see-into. I would very much like to see some proof
> of performance problems before we worry about this.
>
>
Does this raise the need for an in-postgres de-fragmenter?
--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com
GTODO