X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1BA9752868 for ; Wed, 18 May 2005 12:50:25 -0300 (ADT) 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 80482-03 for ; Wed, 18 May 2005 15:50:23 +0000 (GMT) Received: from mx-00.sil.at (mx-00.sil.at [62.116.68.196]) by svr1.postgresql.org (Postfix) with ESMTP id 849CD5280B for ; Wed, 18 May 2005 12:50:21 -0300 (ADT) Received: (qmail-ldap/ctrl 35887 invoked from network); 18 May 2005 15:50:18 -0000 Received: from unknown (HELO jupiter.sonorys.at) ([213.235.243.42]) (envelope-sender ) by mx-00.sil.at (qmail-ldap-1.03) with SMTP for ; 18 May 2005 15:50:18 -0000 Received: from neptun.sonorys.at (neptun.sonorys.at [172.24.1.17]) by jupiter.sonorys.at (8.11.7+Sun/8.11.7) with ESMTP id j4IFoK128994 for ; Wed, 18 May 2005 17:50:20 +0200 (MEST) Received: by neptun.sonorys.at with Internet Mail Service (5.5.2653.19) id <2JD5WT8A>; Wed, 18 May 2005 17:50:20 +0200 Message-ID: From: =?ISO-8859-1?Q?K=D6PFERL_Robert?= To: Cc: Sql-Postgre Subject: Meaning of ERROR: tuple concurrently updated Date: Wed, 18 May 2005 17:50:18 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200505/148 X-Sequence-Number: 21461 Hi, I have got some kind of FIFO-queue table. New records are inserted and the oldest are DELETEd. Thus I run VACUUM ANALYZE; every night by cron. However I keep getting ERROR: tuple concurrently updated My research lead me to the point that this is VACUUM tothether with the INSERTs being issued to that table all the time. But I didn't find a solution to avoid this. AFAIK now the table never gets VACUUMed at all? Please, what's really about that, how can it be avoided? Thanks in advance