| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, 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-11 01:08:47 |
| Message-ID: | 20080311010847.GM8199@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut wrote:
> 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.
Also it would get more buildfarm coverage if it were default. If it
breaks something we'll notice earlier.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-11 01:42:33 | LISTEN vs. two-phase commit |
| Previous Message | Tom Lane | 2008-03-10 23:20:43 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-11 01:45:48 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |
| Previous Message | Tom Lane | 2008-03-10 23:20:43 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |