Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Fix for large file support (nonsegment mode support)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] Fix for large file support (nonsegment mode support)
Date: 2008-03-10 23:11:43
Message-ID: 200803110011.45816.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> > There is latest version of nonsegment support patch. I changed
> > LET_OS_MANAGE_FILESIZE to USE_SEGMENTED_FILES and I added
> > -disable-segmented-files switch to configure. I kept tuplestore behavior
> > and it still split file in both mode.
>
> Applied with minor corrections.

Why is this not the default when supported?  I am wondering both from the 
point of view of the user, and in terms of development direction.

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-03-10 23:20:43
Subject: Re: [PATCHES] Fix for large file support (nonsegment mode support)
Previous:From: Stephen DenneDate: 2008-03-10 20:57:15
Subject: Re: Maximum statistics target

pgsql-patches by date

Next:From: Tom LaneDate: 2008-03-10 23:20:43
Subject: Re: [PATCHES] Fix for large file support (nonsegment mode support)
Previous:From: Simon RiggsDate: 2008-03-10 22:00:27
Subject: Re: Very slow (2 tuples/second) sequential scan afterbulk insert; speed returns to ~500 tuples/second after commit

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group