Postgres crash? could not write to log file: No space left on device - Mailing list pgsql-bugs

From Yuri Levinsky
Subject Postgres crash? could not write to log file: No space left on device
Date
Msg-id B72526FA2066E344AFD09734A487318103E9294E@falcon1.celltick.com
Whole thread Raw
Responses Re: Postgres crash? could not write to log file: No space left on device
Re: Postgres crash? could not write to log file: No space left on device
List pgsql-bugs
Dear All,

I have the following issue on Sun Solaris 10. PostgreSQL version is
9.2.3. The wall logging is minimal and no archiving. The DB restarted
several time, the box is up for last 23 days. The PostgreSQL
installation and files under /data/postgres that is half empty. Is it
some other destination that might cause the problem? Can I log the space
consumption and directory name where the problem is happening by some
debug level or trace setting? =20

=20

PANIC:  could not write to log file 81, segment 125 at offset 13959168,
length 1392640: No space left on device

LOG:  process 10203 still waiting for ShareLock on transaction 3010915
after 1004.113 ms

STATEMENT:  UPDATE tctuserinfo SET clickmiles =3D clickmiles + $1,
periodicalclickmiles =3D periodicalclickmiles + $2, active =3D $3,
activeupdatetime =3D $4, activationsetby =3D $5, smscid =3D $6, sdrtime =
=3D $7,
simvalue =3D simvalue + $8, totalsimval

ue =3D totalsimvalue + $9, firstclick =3D $10, lastclick =3D $11,
firstactivationtime =3D $12, cbchannel =3D $13, clickmilesupdatetime =3D =
$14,
ci =3D $15, lac =3D $16, bscid =3D $17, lastlocationupdatetime =3D $18,
subscriptiontype =3D $19, contentcategory =3D

$20, livechannels =3D $21, contextclicks =3D $22 WHERE phonenumber =3D =
$23

LOG:  WAL writer process (PID 10476) was terminated by signal 6

LOG:  terminating any other active server processes

FATAL:  the database system is in recovery mode

=20

But it looks OK:

=20

dbnetapp:/vol/postgres

                        90G    44G    46G    49%    /data/postgres

=20

Is it possible that "heavy" queries consuming disk space (as temporary
space) and after the crash and recovery it becoming OK?=20

=20

pgsql-bugs by date:

Previous
From: Amit Kapila
Date:
Subject: Re: BUG #8242: No way to debug "subquery must return only one column" error
Next
From: Tom Lane
Date:
Subject: Re: Postgres crash? could not write to log file: No space left on device