From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: 彭昱傑 <k872892@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Too many .history file in pg_xlog takes lots of space
Date: Wed, 14 Mar 2018 11:29:44 -0400
Message-ID: <25800.1521041384@sss.pgh.pa.us> (raw)
In-Reply-To: <20180314134958.yzp2pze2s2yajf7k@alvherre.pgsql>
References: <20180314134958.yzp2pze2s2yajf7k@alvherre.pgsql>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, k872892@gmail.com
Subject: Re: Too many .history file in pg_xlog takes lots of space
In-Reply-To: <25800.1521041384@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox