Re: Too many .history file in pg_xlog takes lots of space

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: 彭昱傑 <k872892(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Too many .history file in pg_xlog takes lots of space
Date: 2018-03-14 15:29:44
Message-ID: 25800.1521041384@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message 彭昱傑 2018-03-15 10:22:18 Re: Too many .history file in pg_xlog takes lots of space
Previous Message Alvaro Herrera 2018-03-14 13:49:58 Re: Too many .history file in pg_xlog takes lots of space