Tom,
There are no any space quota on user postgres. It always happens on
different log files. When I am creating huge dummy file in same FS -
nothing wrong.=20
P.S. I am getting same error when I am using pg_dump in tar format. I
don't know if there is some relation between 2 issues. The reason of the
pg_dump space failure is: when using tar format, pg_dump write temporary
data into /var, which might be smaller than biggest table requires. The
fix is simple in this case: to use custom format or increase /var. I
actually don't know what PostgreSQL has to do in /var and if it is same
problem? By the way it's impossible to understand where not enough space
from pg_dump output as well as in my original issue.=20
Sincerely yours,
Yuri Levinsky, DBA
Celltick Technologies Ltd., 32 Maskit St., Herzliya 46733, Israel
Mobile: +972 54 6107703, Office: +972 9 9710239; Fax: +972 9 9710222
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]=20
Sent: Tuesday, June 25, 2013 4:47 PM
To: Yuri Levinsky
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Postgres crash? could not write to log file: No
spaceleft on device
"Yuri Levinsky" <yuril@celltick.com> writes:
> I have the following issue on Sun Solaris 10. PostgreSQL version is=20
> 9.2.3. The wall logging is minimal and no archiving. The DB restarted=20
> several time, the box is up for last 23 days. The PostgreSQL=20
> installation and files under /data/postgres that is half empty. Is it=20
> some other destination that might cause the problem? Can I log the=20
> space consumption and directory name where the problem is happening by
> some debug level or trace setting?
> PANIC: could not write to log file 81, segment 125 at offset=20
> 13959168, length 1392640: No space left on device
That's definitely telling you it got ENOSPC from a write in
$PGDATA/pg_xlog. Maybe you have a user-specific space quota affecting
the postgres account?
regards, tom lane