| From: | "Zeugswetter Andreas OSB SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "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 08:51:17 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57902DD3018@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> > 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.
No we don't, because the buildfarm does not test huge files.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2008-03-11 09:42:28 | strange pg_ctl's behavior |
| Previous Message | Zeugswetter Andreas OSB SD | 2008-03-11 08:49:59 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-03-11 09:58:20 | Re: Very slow (2 tuples/second) sequential scan afterbulk insert; speed returns to ~500 tuples/second after commit |
| Previous Message | Zeugswetter Andreas OSB SD | 2008-03-11 08:49:59 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |