Re: 2GB limit for temp_file_limit on 32bit platform

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Christopher Browne <cbbrowne(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 2GB limit for temp_file_limit on 32bit platform
Date: 2012-07-19 21:08:05
Message-ID: 50087735.8050804@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 07/19/2012 01:48 PM, Christopher Browne wrote:
>
> On Thu, Jul 19, 2012 at 4:29 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>>
>> On 07/19/2012 01:04 PM, Pavel Stehule wrote:
>>>
>>> I did a backport of temp_file_limit feature to 9.1, but when we tested
>>> this patch, we found very restristrictive limit to 2GB.
>>>
>>> 2GB is nonsense, because this is session limit of temp files, and
>>> these files should be longer than 2GB.
>>
>>
>> I haven't read the patch but... don't all 32bit platforms have a 2GB limit
>> (by default)?
>
> I don't think so.
>
> LFS got done in the mid-90s, which is long enough ago for people to
> start forgetting about it. Are there any supported platforms that
> didn't adopt LFS?
>
> http://en.wikipedia.org/wiki/Large_file_support

Note: "by default" :). I know they could support LFS but as I recall you
had to compile specifically for it (at least on linux and old versions
of pg).

So I was curious if it was that specific limitation or a limitation
within the Pg code itself.

Sincerely,

Joshua D. Drake

--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2012-07-19 21:58:19 Re: 2GB limit for temp_file_limit on 32bit platform
Previous Message Tom Lane 2012-07-19 21:02:08 Re: [PERFORM] DELETE vs TRUNCATE explanation