X-Original-To: pgsql-sql@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4816C4764E6 for ; Tue, 6 May 2003 10:28:17 -0400 (EDT) Received: from matrix.gatewaynet.com (unknown [217.19.69.50]) by postgresql.org (Postfix) with ESMTP id 1306C4764C4 for ; Tue, 6 May 2003 10:28:15 -0400 (EDT) Received: from matrix.gatewaynet.com (localhost [127.0.0.1]) by matrix.gatewaynet.com (8.12.5/8.12.5) with ESMTP id h46JWN1s023401; Tue, 6 May 2003 17:32:23 -0200 Received: from localhost (achill@localhost) by matrix.gatewaynet.com (8.12.5/8.12.5/Submit) with ESMTP id h46JWNTK023397; Tue, 6 May 2003 17:32:23 -0200 Date: Tue, 6 May 2003 17:32:23 -0200 (GMT+2) From: Achilleus Mantzios To: SZUCS Gabor Cc: pgsql-sql@postgresql.org Subject: Re: VACUUM FULL and ALTER TABLE do *nothing* in 7.3.2 In-Reply-To: <008801c313d6$ad89e390$0a03a8c0@fejleszt2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-38.6 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, QUOTE_TWICE_1,REPLY_WITH_QUOTES,SIGNATURE_LONG_DENSE, USER_AGENT_PINE autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200305/87 X-Sequence-Number: 13252 On Tue, 6 May 2003, SZUCS Gabor wrote: > Dear Achilleus, > > Dunno, it's a multiuser environment. However, I'll try asking everyone to > stop working for a minute... > > ... oops, I just see that it finished about half an hour before (taking an > amazing 76 minutes for ALTER TABLE to complete). About that time, I started > and exited a client. Seems it solved the problem. Now "vacuum full analyze" > finished in a couple of seconds. > > Do you have any idea about an explanation? Does vacuum wait for the end of > each and every transaction? Just take a look at http://www.postgresql.org/docs/view.php?version=7.3&idoc=1&file=sql-lock.html VACUUM FULL acquires a ACCESS EXCLUSIVE MODE. That means that if a table is accessed in any way the VACUUM FULL command will wait. Open Cursors might be a reason. > > G. > -- > while (!asleep()) sheep++; > > ---------------------------- cut here ------------------------------ > ----- Original Message ----- > From: "Achilleus Mantzios" > Sent: Tuesday, May 06, 2003 7:53 PM > > > Maybe its a locking issue. > > Did you quit any app using the DB? > Did you commit/rollback all pending transactions (if any)? > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > -- ================================================================== Achilleus Mantzios S/W Engineer IT dept Dynacom Tankers Mngmt Nikis 4, Glyfada Athens 16610 Greece tel: +30-210-8981112 fax: +30-210-8981877 email: achill@matrix.gatewaynet.com mantzios@softlab.ece.ntua.gr