From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Raghavendra Rao J S V <raghavendrajsv(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: org.postgresql.util.PSQLException: Error could not open file "base/": No such file or directory |
Date: | 2018-03-06 05:13:08 |
Message-ID: | 0157eb17-e631-da92-e842-51e4c30dd575@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-03-06 05:23:41 | Re: Resync second slave to new master |
Previous Message | Adrian Klaver | 2018-03-06 05:06:55 | Re: What is wrong with my pgadmin? |