Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 6565F1337B86 for ; Wed, 3 Nov 2010 13:06:14 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 40856-07 for ; Wed, 3 Nov 2010 16:06:07 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.sdb.it (mail.sdb.it [212.141.11.2]) by mail.postgresql.org (Postfix) with ESMTP id 43C2D1337B6E for ; Wed, 3 Nov 2010 13:06:06 -0300 (ADT) Received: by mail.sdb.it (Postfix, from userid 500) id 2E0EF8074; Wed, 3 Nov 2010 17:06:04 +0100 (CET) Received: from geronimo.sdb.it (geronimo.sdb.it [10.101.1.20]) by mail.sdb.it (Postfix) with ESMTP id 2911B8021 for ; Wed, 3 Nov 2010 17:06:04 +0100 (CET) Received: from mailtech.sdb.it (sdbit-srv01.sdb.it [10.118.122.250]) by geronimo.sdb.it (Postfix) with ESMTP id 3FD29381B1D for ; Wed, 3 Nov 2010 17:05:53 +0100 (CET) Received: from [10.118.101.88] (silviob.sdb.it [10.118.101.88]) by mailtech.sdb.it (Postfix) with ESMTP id 1218C58ABA for ; Wed, 3 Nov 2010 17:06:04 +0100 (CET) Message-ID: <4CD1886C.5000503@tech.sdb.it> Date: Wed, 03 Nov 2010 17:06:04 +0100 From: Silvio Brandani User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: PANIC killing vacuum process Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Private-Material: Please read notice X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.011 tagged_above=-10 required=5 tests=BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201011/14 X-Sequence-Number: 35980 Alls, we have develop a script to execute the vacuum full on all tables of our very big database , since it is a 24 x 7 available system we have not a timeframe to exec the vacuum full. so we try with this script running the vauum full table by table and if the vacuum generate the waiting status for other connections we kill the vacuum . But we encounter following problem: with kill command: 2010-11-03 14:25:27 CET [19324]: [4-1] FATAL: terminating connection due to administrator command 2010-11-03 14:25:27 CET [19324]: [5-1] STATEMENT: vacuum full analyze verbose tracking.as_history_status ; 2010-11-03 14:25:27 CET [19324]: [6-1] PANIC: cannot abort transaction 75073917, it was already committed with pg_cancel_backend(pid) command: CPU 0.18s/0.26u sec elapsed 3.79 sec. ERROR: canceling statement due to user request PANIC: cannot abort transaction 75081452, it was already committed server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !> quit -> \q the server crash and we have a service unavailiability on our production system. Is it possible to softly kill a vacuum process without risk a panic ????? thanks a lot Silvio Brandani --- Utilizziamo i dati personali che la riguardano esclusivamente per nostre finalitą amministrative e contabili, anche quando li comunichiamo a terzi. Informazioni dettagliate, anche in ordine al Suo diritto di accesso e agli altri Suoi diritti, sono riportate alla pagina http://www.savinodelbene.com/privacy.html Se avete ricevuto questo messaggio per errore Vi preghiamo di ritornarlo al mittente eliminandolo assieme agli eventuali allegati, ai sensi art. 616 codice penale http://www.savinodelbene.com/privacy/codice_penale_616.html L'Azienda non si assume alcuna responsabilitą giuridica qualora pervengano da questo indirizzo messaggi estranei all'attivitą lavorativa o contrari a norme. --