Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id C19CA9F9756 for ; Tue, 16 Oct 2007 01:03:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 07816-04 for ; Tue, 16 Oct 2007 01:03:15 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by postgresql.org (Postfix) with ESMTP id 859569F964A for ; Tue, 16 Oct 2007 01:03:15 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so19649ugf for ; Mon, 15 Oct 2007 21:03:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=xxkizfgDx3B0ilw1I0wtGcCUQf4rugTXRpKA7Xtvljs=; b=ubsd9ebzVa1bUFIZWAPH2nHDv5a1CN+cGmzUgoqyWZiMv7D4n8BTnN67Zs1xrq8qHfbEveCkeN4OZdSZE0mBGKK6LKAB+q0vFk3rbMiQkj/eUuT34nvNRCoGvBAaFEpP1kTP6DXyuyx8/Ay2ZQ/U+WZ9H5qzq/7HtR2d75AfqqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=feXDR144iotZblLR3mTiARvNGXpUruROx48RsQn6Nws6zfbCYecdlWBEBXpG9vbCvlX0IA1mLZO6zZlMD2HW4o+r9tUw7cNrbOpnk2QZH8xL+gmV+b0++szMumIhzcl9JSU8hJEZW5toJa5XsL00bDB2nLGe7bd0kp55329mi0k= Received: by 10.67.116.4 with SMTP id t4mr8642711ugm.1192507394295; Mon, 15 Oct 2007 21:03:14 -0700 (PDT) Received: by 10.67.29.6 with HTTP; Mon, 15 Oct 2007 21:03:14 -0700 (PDT) Message-ID: Date: Mon, 15 Oct 2007 23:03:14 -0500 From: "Scott Marlowe" To: "Darren Reed" Subject: Re: Is my database now too big? Cc: "Tom Lane" , "Joshua D. Drake" , pgsql-admin@postgresql.org In-Reply-To: <471435D1.4030806@fastmail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1191730382.18880.1214536197@webmail.messagingengine.com> <47097EA7.902@fastmail.net> <4712D97E.7010004@fastmail.net> <4712E15B.8000405@fastmail.net> <17093.1192464190@sss.pgh.pa.us> <4713CA8C.5020303@fastmail.net> <471435D1.4030806@fastmail.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/135 X-Sequence-Number: 27049 On 10/15/07, Darren Reed wrote: > Scott Marlowe wrote: > > ... > > > > Again, I'm kinda shooting in the dark here as you reveal more and more > > what you are doing a little at a time. A test case that can invoke > > this failure would be most useful. > > > After seeing this today: > ERROR: duplicate key violates unique constraint "ers_pkey" > ERROR: duplicate key violates unique constraint "foo_pkey" > ERROR: duplicate key violates unique constraint "foo_pkey" > ERROR: duplicate key violates unique constraint "foo_pkey" > ERROR: duplicate key violates unique constraint "foo_pkey" > ERROR: duplicate key violates unique constraint "foo_pkey" > ERROR: could not open segment 1 of relation 1663/10793/2659 (target > block 858862642): No such file or directory > ERROR: could not open segment 1 of relation 1663/10793/2659 (target > block 858862642): No such file or directory > ERROR: could not open segment 1 of relation 1663/10793/2659 (target > block 858862642): No such file or directory > ERROR: could not open segment 1 of relation 1663/10793/2659 (target > block 858862642): No such file or directory > ... > > ...there was little or no activity during this time, apart from > some inserts, maybe some selects, etc. Nothing that should > have caused this kind of upset. > > There is a file that matches this: > -rw------- 1 postgres wheel 57344 Oct 14 22:57 > /data/db/second/base/10793/2659 > but it isn't in the directory where I moved most of the indexes to: > ls /data/index/ext/10793/ > 16390 16397 16399 16406 16407 16410 16414 16425 16434 16435 How, exactly, did you move those indexes?