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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-10 23:20:43 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |
Previous Message | Stephen Denne | 2008-03-10 20:57:15 | Re: Maximum statistics target |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-10 23:20:43 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |
Previous Message | Simon Riggs | 2008-03-10 22:00:27 | Re: Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit |