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 1er95R-0003wc-2u for pgsql-admin@arkaria.postgresql.org; Wed, 28 Feb 2018 21:16:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1er95Q-0001Wj-3z for pgsql-admin@arkaria.postgresql.org; Wed, 28 Feb 2018 21:16:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1er95P-0001WZ-H0 for pgsql-admin@lists.postgresql.org; Wed, 28 Feb 2018 21:16:27 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1er95M-0002vS-G6 for pgsql-admin@postgresql.org; Wed, 28 Feb 2018 21:16:26 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 4847B20C8D; Wed, 28 Feb 2018 16:16:23 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 28 Feb 2018 16:16:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=DBOo3kAbu6ouH2yXvUtPxmoEoJy4k eKo8elF54O0Q8A=; b=ciuqVjlItXODZ2F4QNRsLibSdnzac82h9JRiR/3Y5q1xP FJEdRDDxoVMaH2DOPfvBBvzCrqIvt7U0YQgF9uj7IaqqMrT5hhsoxi/24TS6Aql9 rv2pKd5UFz0ZaY0fT54D6gMCtB0YH0XSCLgyMR2LLxondTec3iC/glabHEOUq7Nc P3ox/0W0s6Af4eMHuk9BmQKo1Q0Z/AhojUhfKTBqOA+OmpalEdppCmIBIK/Nte6s bM0VKhkSjhGHWgZCzAdYMr6+u+ejgkKGeCIMePB29C+htMmcTsRNfYcrK9ls2XhV 2CLuE4snTuDsOiwcyor7lGLQ/HoUINXmJVD98cFKw== X-ME-Sender: Received: from intern.anarazel.de (unknown [136.24.76.189]) by mail.messagingengine.com (Postfix) with ESMTPA id EDA387E141; Wed, 28 Feb 2018 16:16:22 -0500 (EST) Date: Wed, 28 Feb 2018 13:16:22 -0800 From: Andres Freund To: Alexandre Garcia Cc: Alvaro Herrera , "pgsql-admin@postgresql.org" Subject: Re: postgresql 9.6 - cannot freeze committed xmax Message-ID: <20180228211621.vikbp5s3rwg47455@alap3.anarazel.de> References: <20180226230931.3m7js5dkzxnu7tbi@alvherre.pgsql> <20180226232113.a3aqlzpckcue4drt@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2018-02-28 21:12:58 +0000, Alexandre Garcia wrote: > Thanks for your answers, took me a little while to restore a backup from > before the upgrade on an empty 9.2 server but here we are => > https://gist.github.com/kuuji/cc73c3c193a0d58aa0e651fbd7bfec58 Thanks. > > > > Prod starting throwing the following errors during autovacuum -> > > 'cannot > > > > freeze committed xmax ' on 2 different tables. Running vacuum > > manually > > > > revealed more tables affected by the same error. What's an example in that message that triggers for problematic_table? I need that to properly interpret the data you provided. Thanks, Andres