Skip site navigation (1) Skip section navigation (2)

Re: pg_dump not enough space to create a backup FreeBSD 6.1?

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: Joost Kraaijeveld <J(dot)Kraaijeveld(at)Askesis(dot)nl>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dump not enough space to create a backup FreeBSD 6.1?
Date: 2007-05-16 16:22:23
Message-ID: 20070516162223.GP14548@nasby.net (view raw or flat)
Thread:
Lists: pgsql-admin
On Wed, May 16, 2007 at 02:36:45PM +0200, Joost Kraaijeveld wrote:
> Hi,
> 
> Running pg_dump on a FreeBSD 6.1 machine gives me:
> 
> [root(at)s13(dot)nedstars(dot)nl:/data/even]# pg_dump -Ft -f ./my_db-2007-5-16.backup -U user my_db
> 
>  /tmp: write failed, filesystem is full
> pg_dump: [tar archiver] could not write to tar member (wrote 0,
> attempted 86)
> 
> pg_dump: *** aborted because of error
> 
> [root(at)s13(dot)nedstars(dot)nl:/data/even]# df -h
> 
> Filesystem       Size    Used   Avail Capacity  Mounted on
> /dev/aacd0s1g    125G    5.8G    109G     5%    /data
> /dev/aacd0s1e    484M     86K    445M     0%    /tmp
> 
> The database is, when dumped in text format and gzipped, 40 Mb, so I
> assume that there is enough space on the /tmp drive to store the temp
> files of the pg_dump.
> 
> Is that assumption OK? Can I somehow use another partition to store the
> temporaray files without changing my /tmp mount?

tar is what's creating the temp files, not pg_dump. AFAIK it obeys the
TEMP environment variable, so changing that should make things good.
-- 
Jim Nasby                                      decibel(at)decibel(dot)org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

In response to

pgsql-admin by date

Next:From: Keaton AdamsDate: 2007-05-16 16:28:29
Subject: WAL file utilization question
Previous:From: Joost KraaijeveldDate: 2007-05-16 12:36:45
Subject: pg_dump not enough space to create a backup FreeBSD 6.1?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group