Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z8FVg-0006xX-7q for pgsql-admin@arkaria.postgresql.org; Thu, 25 Jun 2015 22:20:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Z8FVf-0006ct-DK for pgsql-admin@arkaria.postgresql.org; Thu, 25 Jun 2015 22:20:39 +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.84) (envelope-from ) id 1Z8FVd-0006ak-Cu for pgsql-admin@postgresql.org; Thu, 25 Jun 2015 22:20:37 +0000 Received: from smtp-auth.no-ip.com ([8.23.224.61] helo=out.smtp-auth.no-ip.com) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Z8FVY-0003Ej-M8 for pgsql-admin@postgresql.org; Thu, 25 Jun 2015 22:20:36 +0000 X-No-IP: alvh.no-ip.org@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from alvin.alvh.no-ip.org (unknown [186.37.114.162]) (Authenticated sender: alvh.no-ip.org@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 883C640101C; Thu, 25 Jun 2015 15:20:24 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id E1DC48F7; Thu, 25 Jun 2015 19:20:21 -0300 (CLT) Date: Thu, 25 Jun 2015 19:20:21 -0300 From: Alvaro Herrera To: Bhanu Gandikota Cc: "pgsql-admin@postgresql.org" Subject: Re: Postgresql 9.3.9 Message-ID: <20150625222021.GN3289@postgresql.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Bhanu Gandikota wrote: > Hi all, > > Does anyone know if we need to run any vacuum (freeze) soon after patching Postgresql to version 9.3.9 [say from 9.3.4]? > Is TXN wrap around fix effective automatically in 9.3.9 or do we have to do anything manually? Look in your log for a message like this shortly after server start: LOG: MultiXact member wraparound protections are now enabled If you see it, then you're fine and nothing is needed. If you see this message instead: LOG: MultiXact member wraparound protections are disabled [...] then autovacuum will have to slowly work its way out of trouble. It might take some time, depending on the database size. You don't need any additional measures as it's automatic. As soon as it has finished, you will see the other message above. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin