X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BF53C329EC2 for ; Wed, 15 Sep 2004 09:37:11 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 20399-09 for ; Wed, 15 Sep 2004 08:37:01 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id EFD13329EB5 for ; Wed, 15 Sep 2004 09:37:02 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i8F8axCp025215 for ; Wed, 15 Sep 2004 08:37:00 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i8F8XmIb024082 for pgsql-admin@postgresql.org; Wed, 15 Sep 2004 08:33:48 GMT From: willmington@gmx.net (R. Willmington) X-Newsgroups: comp.databases.postgresql.admin Subject: VACUUM FULL achieves nothing / Postgres 7.3.2 + RedHat 7.3 Date: 15 Sep 2004 01:33:50 -0700 Organization: http://groups.google.com Lines: 35 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/145 X-Sequence-Number: 14848 Ladies and gentlemen, I am running a Postgres 7.3.2 on a Red Hat Linux release 7.3 (Valhalla) in a multiprocessor (4) environment. There is a db table in one of the databases containing some 20.000 records updated on a daily basis. When attempting to delete about 4000 deprecated records from it the query ran for almost half an hour and postmaster occupied 100% CPU, so i decided to cancel it. (Note: select querys run fine and finish within milliseconds). In order to reproduce the problem, i copied the above database to my staging system (same linux, same postgres), and ran a vacuum full analyze. It finished after 33 minutes. After the vacuum full the deletion from the 20.000 records table succeeded within 23 ms. Now, here's the problem: When running the VACUUM FULL on the live system, it finished after 20 Seconds (without error messages) - and did not change anything. Performance is still bad, and the delete from xxx where ... still takes forever. Additional information: The applications using the database are java - based and create persistent connections (from a connection pool) to the postgres database. These connections are on autocommit, thus, there should not be any opened transactions preventing the vacuum full from write - locking the tables. Any idea what i am doing wrong? Any help appreciated. Kind regards, R. Willmington