Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id B4D13DA629A for ; Wed, 1 Aug 2012 17:18:44 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SwfNT-0006WD-MS for pgsql-admin@postgresql.org; Wed, 01 Aug 2012 20:18:44 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q71KIRo4022290; Wed, 1 Aug 2012 16:18:27 -0400 (EDT) From: Tom Lane To: Gary Webster cc: pgsql-admin@postgresql.org Subject: Re: [pgsql] How bad is this full vacuum error? In-reply-to: References: Comments: In-reply-to Gary Webster message dated "Wed, 01 Aug 2012 11:43:24 -0400" Date: Wed, 01 Aug 2012 16:18:27 -0400 Message-ID: <22289.1343852307@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201208/7 X-Sequence-Number: 39828 Gary Webster writes: > How bad is this? > 2012-08-01 06:30:03 PDT 15961 [local] cp_repository_na2 ERROR: missing > chunk number 0 for toast value 1086399 in pg_toast_987417 > 2012-08-01 06:30:03 PDT 15961 [local] cp_repository_na2 STATEMENT: VACUUM > (FULL); If it's repeatable, it's corrupted data :-(. If it just happened once, and doesn't recur on the next try, it might have been related to a system catalog race condition that we fixed last fall. (What PG version are you running?) I'm unsure about that though, because the toast table name seems to indicate that it's for a user table not a system catalog, and I'm not very sure why VACUUM would be doing toast dereferences into a user table. regards, tom lane