Subject | Re: [firebird-support] TMP space required during restore |
---|---|
Author | Ann Harrison |
Post date | 2012-01-24T20:17:22Z |
Rick Debay wrote:
Thomas Steinmaurer <ts@...> wrote:
use the whole record, just the key, the record number, and a small
amount of overhead. The sort is done for each index, and no sorts are
done in parallel. If you have lots of small tables, you'll need
less space than if you have a few very large tables. The amount of
space used is determined by the index with the largest key in the
largest table and may require considerably more space than the index
it eventually creates if sub-sorts have to be merged to disk.
Good luck,
Ann
>> gbak: ERROR: I/O error for file "/tmp/fb_sort__M9plMy"More.
>> gbak: ERROR: Error while trying to write to file
>> gbak: ERROR: No space left on device
>>
>>
>> We've started getting this error when restoring an 11GB database. How
>> much space should we estimate for temp files?
Thomas Steinmaurer <ts@...> wrote:
> Twice the size is an old and possibly still a good guess, I think. ItEach table must be sorted for each index defined. The sort doesn't
> all depends on the number and size of the indices.
use the whole record, just the key, the record number, and a small
amount of overhead. The sort is done for each index, and no sorts are
done in parallel. If you have lots of small tables, you'll need
less space than if you have a few very large tables. The amount of
space used is determined by the index with the largest key in the
largest table and may require considerably more space than the index
it eventually creates if sub-sorts have to be merged to disk.
Good luck,
Ann