Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ew6nN-0000pS-1S for pgsql-performance@arkaria.postgresql.org; Wed, 14 Mar 2018 13:50:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ew6nL-0005mr-Nv for pgsql-performance@arkaria.postgresql.org; Wed, 14 Mar 2018 13:50:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ew6nL-0005mU-GT for pgsql-performance@lists.postgresql.org; Wed, 14 Mar 2018 13:50:19 +0000 Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ew6nI-0005O7-2T for pgsql-performance@postgresql.org; Wed, 14 Mar 2018 13:50:18 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 20F421096; Wed, 14 Mar 2018 09:50:01 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 14 Mar 2018 09:50:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Uc4JKlmrb+EcsYHZi ORAZCTAcjuzUdl3sJ9PKLk4+5w=; b=Tcp6Oq6wHMI+P5RH6vwGllqPwGBj30fJZ wSIigfZ+DWk8xooEwasLTHk7QHaT4zTF+tnT2DAdu5SlIwuh52kHqHB7oOkxUg91 loLTHcyE0Eya9giYNCOv3yKyGCVGWBe4NPFHnqbP4siZd9ds0w/o3nR6bo0NXIsQ 2E+5XxXaMLgAotQXxtOB2w/Z9g4HEt/0gnrYwaSfSYElWJJgzNfK+BVGHnoAxdJa /9NitjI7ZXiMFjIs7m21TIA1m3IeFILrEPIWI4lsMvk/MrxZ09zC508uIxXgYkwt 6Ma8Q4t/xwe4LYmhB1HRKa+HV4YRZdkqfyAnZJVedQnNICz1FcN3w== X-ME-Sender: Received: from alvin.alvh.no-ip.org (unknown [179.56.29.253]) by mail.messagingengine.com (Postfix) with ESMTPA id 5290B7E0F1; Wed, 14 Mar 2018 09:50:00 -0400 (EDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 479B0AA4; Wed, 14 Mar 2018 10:49:58 -0300 (-03) Date: Wed, 14 Mar 2018 10:49:58 -0300 From: Alvaro Herrera To: =?utf-8?B?5b2t5pix5YKR?= Cc: pgsql-performance@postgresql.org Subject: Re: Too many .history file in pg_xlog takes lots of space Message-ID: <20180314134958.yzp2pze2s2yajf7k@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 彭昱傑 wrote: > My postgre version is 9.4.9, and I face a space issue. Latest in 9.4 is 9.4.17, so you're missing about two years of bug fixes. > 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. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services