X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 30E773A3D48 for ; Tue, 16 Nov 2004 16:57:29 +0000 (GMT) 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 06307-01 for ; Tue, 16 Nov 2004 16:57:25 +0000 (GMT) Received: from web12704.mail.yahoo.com (web12704.mail.yahoo.com [216.136.173.241]) by svr1.postgresql.org (Postfix) with SMTP id 2086A3A3C4A for ; Tue, 16 Nov 2004 16:57:24 +0000 (GMT) Received: (qmail 69392 invoked by uid 60001); 16 Nov 2004 16:57:14 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=EOFUhWnUH+NdaVif53ryRLm5S2YTCIIKRCqTgRU4YBCPwYXCNvX389jSwD1jWdwaNAOmrCQ6kEmMcigwPsJ1Yxj4sk2xXniiv1PPInlFITnDoU183iXG9jLkm96O+4Vq9anepmdvdN6hn8EVtviUDYBlAAUUogIKL973yyxgsr0= ; Message-ID: <20041116165711.69388.qmail@web12704.mail.yahoo.com> Received: from [216.194.17.194] by web12704.mail.yahoo.com via HTTP; Tue, 16 Nov 2004 08:57:11 PST Date: Tue, 16 Nov 2004 08:57:11 -0800 (PST) From: Reply-To: ogjunk-pgjedan@yahoo.com Subject: Re: cannot open segment 1 of relation .... No such file or directory To: pgsql-admin@postgresql.org In-Reply-To: <8972.1100538564@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200411/135 X-Sequence-Number: 15519 Hello, --- Tom Lane wrote: > writes: > > I'm using PG 7.3.4 under RedHat 9.0 and I've started noticing the > > following type of errors: > > cannot open segment 1 of relation url (target block 537329664): > No > > such file or directory > > If this is coming from an indexscan query, then I'd bet on the > problem > being a corrupted index on the "url" table. REINDEX may get you out > of it. If not, try dumping and reloading that table (or the whole > database if need be). Thanks, I'll try REINDEX shortly. Before I do that, though, I'm wondering if it's somehow possible to get the details of this problem - I'd love to see which DB file PG is actually looking for. > 7.3.4 is a bit old --- you should at least move up to 7.3.8, if not > 7.4.something. Thanks for the info - I'll upgrade to 7.3.8 then, too. Otis