From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zeugswetter Andreas OSB SD <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>, pgsql-patches(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: [PATCHES] Fix for large file support (nonsegment mode support) |
Date: | 2008-03-11 17:39:13 |
Message-ID: | 200803111839.15657.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Zdenek Kotala wrote:
> Yes, agree. It seems only ZFS is OK at this moment and if somebody sets
> 32TB he gets nonsegment mode anyway.
Surely if you set the segment size to INT64_MAX, you will get nonsegmented
behavior anyway, so two code paths might not be necessary at all.
> I looked into posix standard and
> there is useful function which can be used. See
>
> http://www.opengroup.org/onlinepubs/009695399/functions/pathconf.html
>
> Maybe we can put additional test into configure and collect appropriate
> data from buildfarm.
It might be good to just check first if it returns realistic values for the
example cases that have been mentioned.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-03-11 17:42:05 | Re: temporal variants of generate_series() |
Previous Message | Greg Smith | 2008-03-11 17:29:02 | Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > > |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-03-11 17:46:23 | Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
Previous Message | Simon Riggs | 2008-03-11 17:31:29 | Re: TransactionIdIsInProgress() cache |