X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EA6CAD1D2B5 for ; Tue, 20 Apr 2004 10:14:02 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 14734-09 for ; Tue, 20 Apr 2004 10:14:05 -0300 (ADT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by svr1.postgresql.org (Postfix) with ESMTP id 377CED1D238 for ; Tue, 20 Apr 2004 10:14:01 -0300 (ADT) Received: from potentialtech.com (pa-plum1c-102.pit.adelphia.net [24.53.179.102]) by internet.potentialtech.com (Postfix) with ESMTP id A556669A71; Tue, 20 Apr 2004 09:14:04 -0400 (EDT) Message-ID: <40852218.2050204@potentialtech.com> Date: Tue, 20 Apr 2004 09:14:00 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Shea,Dan [CIS]" Cc: 'Christopher Kings-Lynne' , pgsql-performance@postgresql.org Subject: Re: Why will vacuum not end? References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_RFCI, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200404/295 X-Sequence-Number: 6595 Shea,Dan [CIS] wrote: > No, but data is constantly being inserted by userid scores. It is postgres > runnimg the vacuum. > Dan. > > -----Original Message----- > From: Christopher Kings-Lynne [mailto:chriskl@familyhealth.com.au] > Sent: Tuesday, April 20, 2004 12:02 AM > To: Shea,Dan [CIS] > Cc: pgsql-performance@postgresql.org > Subject: Re: [PERFORM] Why will vacuum not end? > >>This vacuum is running a marathon. Why will it not end and show me free >>space map INFO? We have deleted a lot of data and I would like to be >>confident that these deletions will be used as free space, rather than >>creating more table files. > > Does another postgres query running have a lock on that table? This may be a dumb question (but only because I don't know the answer) Doesn't/shouldn't vacuum have some kind of timeout so if a table is locked it will give up eventually (loudly complaining when it does so)? -- Bill Moran Potential Technologies http://www.potentialtech.com