From: | Farhan Malik <malikpiano(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Out of space making backup |
Date: | 2009-12-25 18:40:47 |
Message-ID: | c2f764400912251040sa32e6ccg3dbc4104ff3f9631@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks. Changing the environmental variable has solved that issue.
It ultimately required 13GB of free space to create a 2GB backup file.
On Fri, Dec 25, 2009 at 1:19 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> Farhan Malik wrote:
>>
>> That sounds right. The error I get from the software is 2009/12/25
>> 10:21:40.812: [00001EA8][ThreadBackupRestore] Restore Error: pg_dump:
>> [tar archiver] could not write to output file: No space left on device
>>
>> Is there a way to have postgre put those large temp files on a
>> different drive? I only have 4GB free on my C: drive and once the
>> temp files go over that I get an out of space error. I have tons of
>> free space on other drives, including the one where I am asking that
>> the final backup.zip file goes.
>>
>> As for changing the backup to a custom format, I will pass that on to
>> the developer of the software.
>>
>
> wild guess says, the value of the TEMP environment variable when the backup
> software is started will determine the path of where that temporary file is
> written. In MS Windows this usually defaults to %USERPROFILE%\Local
> Settings\Temp\
>
>
--
Please note my new email address malikpiano(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2009-12-25 19:03:33 | Re: Finding the bin path |
Previous Message | Mark Morgan Lloyd | 2009-12-25 18:27:09 | Re: Updating from 8.2 to 8.4 |