On 22.12.2010 09:25, Rob Wultsch wrote:
On Wed, Dec 22, 2010 at 12:15 AM, Heikki Linnakangas
wrote:
Hmm, innodb_autoextend_increment seems more like what we're discussing here
(http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#sysvar_innodb_autoextend_increment).
If I'm reading tha
On Wed, Dec 22, 2010 at 12:15 AM, Heikki Linnakangas
wrote:
> On 22.12.2010 03:45, Rob Wultsch wrote:
>>
>> On Tue, Dec 21, 2010 at 4:49 AM, Robert Haas
>> wrote:
>>>
>>> On Sun, Dec 19, 2010 at 1:10 PM, Jim Nasby wrote:
On Dec 19, 2010, at 1:10 AM, flyusa2010 fly wrote:
>
> Do
On 22.12.2010 03:45, Rob Wultsch wrote:
On Tue, Dec 21, 2010 at 4:49 AM, Robert Haas wrote:
On Sun, Dec 19, 2010 at 1:10 PM, Jim Nasby wrote:
On Dec 19, 2010, at 1:10 AM, flyusa2010 fly wrote:
Does postgres make an effort to create a file with physically continuous blocks?
AFAIK all files
On Tue, Dec 21, 2010 at 4:49 AM, Robert Haas wrote:
> On Sun, Dec 19, 2010 at 1:10 PM, Jim Nasby wrote:
>> On Dec 19, 2010, at 1:10 AM, flyusa2010 fly wrote:
>>> Does postgres make an effort to create a file with physically continuous
>>> blocks?
>>
>> AFAIK all files are expanded as needed. I d
On Sun, Dec 19, 2010 at 1:10 PM, Jim Nasby wrote:
> On Dec 19, 2010, at 1:10 AM, flyusa2010 fly wrote:
>> Does postgres make an effort to create a file with physically continuous
>> blocks?
>
> AFAIK all files are expanded as needed. I don't think there's any flags you
> can pass to the filesyst
On Dec 19, 2010, at 1:10 AM, flyusa2010 fly wrote:
> Does postgres make an effort to create a file with physically continuous
> blocks?
AFAIK all files are expanded as needed. I don't think there's any flags you can
pass to the filesystem to tell it "this file will eventually be 1GB in size".