Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X4WII-0001Kp-CK for pgsql-general@arkaria.postgresql.org; Tue, 08 Jul 2014 14:22:54 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X4WIH-0007KR-O3 for pgsql-general@arkaria.postgresql.org; Tue, 08 Jul 2014 14:22:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X4WIG-0007KH-Jo for pgsql-general@postgresql.org; Tue, 08 Jul 2014 14:22:52 +0000 Received: from nm9-vm6.bullet.mail.ne1.yahoo.com ([98.138.91.102]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X4WI7-0005yP-Jd for pgsql-general@postgresql.org; Tue, 08 Jul 2014 14:22:51 +0000 Received: from [98.138.226.178] by nm9.bullet.mail.ne1.yahoo.com with NNFMP; 08 Jul 2014 14:22:39 -0000 Received: from [98.138.87.3] by tm13.bullet.mail.ne1.yahoo.com with NNFMP; 08 Jul 2014 14:22:39 -0000 Received: from [127.0.0.1] by omp1003.mail.ne1.yahoo.com with NNFMP; 08 Jul 2014 14:22:39 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 720741.79942.bm@omp1003.mail.ne1.yahoo.com Received: (qmail 4899 invoked by uid 60001); 8 Jul 2014 14:22:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1404829359; bh=NqFQIV4iSRmxKCw8PsaIAEue5H69Ih1oLO+0ZFx+V2w=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=UTr6yn7o68+njHP2IoKmH0OcwuCUngekp/0n0tl+IvV/O+iulbsbwCr2Lm0hMDpaeTblfV/QZz+WXWH8eXf1ywa5A7tPIZcF53e2sDXiJu2Y+l4BfQ/Z0n8R4/K5av+Mu7x0uAK9cV7uB6JvLB9JjL+SLBclEur9m/5QTPJMe08= X-YMail-OSG: wjdHzVMVM1kQLVQKQc573dlfkNihnTdfkdig66qzwuTo6Ye 5E3mFqxhj7nD8ZoBcj9pvdfdWHAOWYX8_Kfv7opGvKUwOghXyH96Eg79B6US Cy_V.UYLV8H_pN5mjdGoxGn6_ws0cTcspvIk75V5LDZuq.._HP6kuXBSRYzH bYJUr2L_7r5D6V5UoHF_nMwgbKlWhKZrXpsxAF5VtMM5bJKgLeefRrd_8AiJ iKeYBSth5xY5VaSnJAeJwvELXbN1KI03V4X2EzM9C.J8pTkvEzPUH5iMoDA1 89vvitoQWmwqBMsOGl8TZ9nhWSTibs_6.TYpqYEOyR.HhLjHgQ4K5SZ0d5Tc MQyf_eoZ4TE9mTX_HDHqDrmZXr05EuAaBeHl5nDn_6eEmBq4YUC8f20zXZ8F E1S5aSEOXpov6zODq3Uu2z.YQPrmOjqATatpQPRcY3EMmfKFBmq15j_bK215 IByWOCnuUDYAdnP8VbVaNOhmvtczOXXGIkI8IvEGP7aPSvHhMHliCFYXUia4 EQa1YDJKl88DqLwY0F7WRtD8HRxo0RnI3YQmAF8QVY0Os4JJY11RCkkuho9s g.0RdKH75wn1.Xtb7lW7RalDk5A7bXQ8QqqFjUawjRWU22xWg.alu1cGCLsT U.42RG1uY2Sq4Q47eVaD7Fi2TfLQuBvTnuuCYukoTEZ3EJSl5heA8ypNI.AC 0mSLKp2IO_AvwV_YG2.N5ng-- Received: from [24.178.25.147] by web122306.mail.ne1.yahoo.com via HTTP; Tue, 08 Jul 2014 07:22:39 PDT X-Rocket-MIMEInfo: 002.001, UHJhYmhqb3QgU2hlZW5hIDxwcmFiaGpvdC5zaGVlbmFAcml2YWx3YXRjaC5jb20.IHdyb3RlOgoKPiBTbyB0aGlzIGlzIHdoYXQgaSBkaWQgYnV0IG15IHByb2JsZW0gaXMgc3RpbGwgbm90IGdvaW5nIGF3YXkuCj4KPiBpIHNodXRkb3duIHRoZSBkYXRhYmFzZSBhbmQgc3RhcnRlZCBpdCBpbiBzaW5nbGUgdXNlciBtb2RlIGFuZAo.IGlzc3VlZCBjb21tYW5kIHZhY3V1bSBmdWxsCj4KPiBUaGUgY29tbWFuZCBjb21wbGV0ZWQgYnV0IHRoZSBpc3N1ZSBzdGlsbCBleGlzdHMKClRoYXQgaXMgdG8gYmUgZXhwZWMBMAEBAQE- X-Mailer: YahooMailWebService/0.8.191.1 References: <53BB25E4.5080400@hogranch.com> <13414.1404774893@sss.pgh.pa.us> Message-ID: <1404829359.42485.YahooMailNeo@web122306.mail.ne1.yahoo.com> Date: Tue, 8 Jul 2014 07:22:39 -0700 From: Kevin Grittner Reply-To: Kevin Grittner Subject: Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions To: Prabhjot Sheena , Tom Lane Cc: John R Pierce , pgsql In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org Prabhjot Sheena wrote: > So this is what i did but my problem is still not going away. > > i shutdown the database and started it in single user mode and > issued command vacuum full > > The command completed but the issue still exists That is to be expected.=A0 The VACUUM FULL command is not useful in this situation.=A0 You need to do a normal VACUUM of the full database, which is something completely different.=A0 You might want to read this blog page for a discussion of this: http://rhaas.blogspot.com/2014/03/vacuum-full-doesnt-mean-vacuum-but.html If you can upgrade to a supported version you will find many improvements to VACUUM in general and autovacuum in particular, but that's probably something to consider after you dig yourself out of the hole you're in now due to inadequate vacuuming. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company --=20 Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general