Re: Too many .history file in pg_xlog takes lots of space - Mailing list pgsql-performance

From Tom Lane
Subject Re: Too many .history file in pg_xlog takes lots of space
Date
Msg-id 25800.1521041384@sss.pgh.pa.us
Whole thread Raw
In response to Re: Too many .history file in pg_xlog takes lots of space  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Too many .history file in pg_xlog takes lots of space  (彭昱傑 <k872892@gmail.com>)
List pgsql-performance
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> 彭昱傑 wrote:
>> Every time I restart postgre server, it generates a new history file:

> That's strange -- it shouldn't happen ... sounds like you're causing a
> crash each time you restart.  Are you using immediate mode in shutdown
> maybe?  If so, don't; use fast mode instead.

I'm confused by this report too.  Plain crashes shouldn't result in
forking a new timeline.  To check, I tried "-m immediate", as well as
"kill -9 postmaster", and neither of those resulted in a new .history file
on restart.  I wonder if the OP's restart process involves calling
pg_resetxlog or something like that (which would be risky as heck).

            regards, tom lane


pgsql-performance by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Too many .history file in pg_xlog takes lots of space
Next
From: 彭昱傑
Date:
Subject: Re: Too many .history file in pg_xlog takes lots of space