Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1et4ua-0002jn-Lo for pgsql-general@arkaria.postgresql.org; Tue, 06 Mar 2018 05:13:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1et4uZ-0001S4-G6 for pgsql-general@arkaria.postgresql.org; Tue, 06 Mar 2018 05:13:15 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1et4uZ-0001Ru-53 for pgsql-general@lists.postgresql.org; Tue, 06 Mar 2018 05:13:15 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1et4uV-000585-Pr for pgsql-general@lists.postgresql.org; Tue, 06 Mar 2018 05:13:13 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 506F520B87; Tue, 6 Mar 2018 00:13:09 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 06 Mar 2018 00:13:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=dkZf6gk2way6hwtg8GTCzqjfZJ2CM oQKHzfWoDptl20=; b=VKqdFP+pwjEA0IxEcwASeRkuJRSajWejX1VR8cR7rZU2O MNVf3xVA4Ie/DxRYW2S+AxoTendIKiHrQwDkW1gSPnFzpO8fiWCV3Z9QkkVaAiY0 zbgIe4L3Vt0qNno30L6S6vjD9kVTUyLcpft38oeok3B3QaWLuPUWS8S32I8sfQJw pIlTNSpUBpwkjXLvPjgAihdWo6ByhmB8pNOEE852rUHhBq4YR3ggWZfDW7LAsCEQ ZFhBM1kO5fb5aOuRkJGAY4fu7K4ZvImPw6EkKlC8GlkZqrbeLpstEzQfU7HAOmrm l7lUVYJBhph+D58v1URLIOGv06T2cjYTIbQUrIuQA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=dkZf6g k2way6hwtg8GTCzqjfZJ2CMoQKHzfWoDptl20=; b=nPQWi1ZdPjN08Se+sVws37 crgYLSqMyf/VvjqSz0ikbkJoO3BhyP7MVmrGvJexyKd3ffumV8k+4f8OhCYE23QD 5+2jC4hINHxf6CCK1sGd3BiyNhvhKVXwpb8RJ5ZgzqlpVlE5Nmn+CNKplKlXQxhI iFGiambJbM8lLfN6mUdl9q/IsHVzXzFpODigMjzukaeEf0bz1oadkqL3KNv8PSKn rEKyk0b82v/XeUh1oN31pDWp1xs4ol+VntoO1u65HY+3QpUi+Nf/U56kZIYWSQRH 9V7NRtvpDPSb3woI2CVvBYaSfLY8wJ6ydk0A9rYpO35AM6YyJ+J5xH8XE4F/VS5g == X-ME-Sender: Received: from [192.168.1.2] (71-35-123-124.tukw.qwest.net [71.35.123.124]) by mail.messagingengine.com (Postfix) with ESMTPA id CEE5A24519; Tue, 6 Mar 2018 00:13:08 -0500 (EST) Subject: Re: org.postgresql.util.PSQLException: Error could not open file "base/": No such file or directory To: Raghavendra Rao J S V , pgsql-general@lists.postgresql.org References: From: Adrian Klaver Message-ID: <0157eb17-e631-da92-e842-51e4c30dd575@aklaver.com> Date: Mon, 5 Mar 2018 21:13:08 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 03/05/2018 05:54 PM, Raghavendra Rao J S V wrote: > Hi, > > Few of the tables and indexes are bloated though auto vacuum has enables. > > Two reclaim the space vacuum, I have ran vacuum full on the larger > tables and also performed reindex on the indexes which are in larger > size. Now the size of the database is in control. > > After perfoming the vacuum full and reindexing on larger tables, I am > facing below error. > > *org.postgresql.util.PSQLException: Error could not open file "base/": > No such file or directory* Assuming the database is up and running then base/ is actually there: https://www.postgresql.org/docs/10/static/storage-file-layout.html When I know a file or directory exists and I see an error like: 'Error could not open file "base/": No such file or directory ' then I generally check permissions on said file/directory. In particular does the app throwing the error having the permissions to 'see' the file/directory? > > Please guide me how to resolve the above error and let me know does this > has any relation with vacumm full or reindexing operation which are > performed by me. > > -- > Regards, > Raghavendra Rao J S V > -- Adrian Klaver adrian.klaver@aklaver.com