From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Wenzhe Zhou <wzhou(at)cisco(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres run out of disk space |
Date: | 2002-12-31 15:53:03 |
Message-ID: | Pine.LNX.4.33.0212310851550.9167-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 30 Dec 2002, Wenzhe Zhou wrote:
> On one of my Linux machine, Postgres server ran out of disk space on its data partition.
> To trace the problem, I turn on Postgres debug log (set debug_level = 2 in conf file).
> We use all of default setting for WAL.
> Accoring to the debug log (postmaster.log), there are only read operations (select query)
> in one hour and twenty minutes. While in that period of time, I saw log messages like
> "DEBUG: recycled transaction log file xxxxxx" in every one minute and used disk space
> increase 105 MB. It looks like the server is busy to write to DB, and transaction log files are recycled in every one minutes. How could this happen? I can't figure out why the
Are you sure there isn't a query like 'update table set a=a+1' kind of
statement going on somewhere? Those queries, that touch everything so
innocently, are often the source of these kinds of problems.
From | Date | Subject | |
---|---|---|---|
Next Message | Martin_Hurst | 2002-12-31 16:06:37 | ODBC - adding missing FROM clause entry |
Previous Message | Martin_Hurst | 2002-12-31 15:37:06 | ODBC - adding missing FROM clause entry |