Re: [PATCHES] Fix for large file support (nonsegment mode support) - Mailing list pgsql-hackers

From Zdenek Kotala
Subject Re: [PATCHES] Fix for large file support (nonsegment mode support)
Date
Msg-id 47D6AE42.7000608@sun.com
Whole thread Raw
In response to Re: [PATCHES] Fix for large file support (nonsegment mode support)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Fix for large file support (nonsegment mode support)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCHES] Fix for large file support (nonsegment mode support)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tom Lane napsal(a):
> "Zeugswetter Andreas OSB SD" <Andreas.Zeugswetter@s-itsolutions.at> writes:
>> Exactly, e.g. AIX is one of those. jfs (not the newer jfs2) has an
>> option
>> to enable large files, which is not the default and cannot be changed
>> post crfs.
>> And even if it is enabled, jfs has a 64 Gb filesize limit !
>> Anybody know others that support large but not huge files ?
>
> Yeah, HPUX 10 is similar --- 128GB hard maximum.  It does say you
> can convert an existing filesystem to largefile support, but it has
> to be unmounted.
>
> These examples suggest that maybe what we want is not so much a "no
> segments ever" mode as a segment size larger than 1GB.

Patch allows to use bigger than 2/4GB segment files and it is possible
changed it in source file. But how it was mentioned in this thread maybe
somethink like this "CREATE TABLESPACE name LOCATION '/my/location'
SEGMENTS 10GB" should good solution. If segments is not mentioned then
default value is used.


            Zdenek

PS: ZFS is happy with 2^64bit size and UFS has 1TB file size limit
(depends on solaris version)

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Autovacuum vs statement_timeout
Next
From: Tom Lane
Date:
Subject: Re: Autovacuum vs statement_timeout