Tom, Martijn,
Thanks very much for your replies.
On Wed, Sep 25, 2002 at 12:55:00AM -0400, Tom Lane wrote:
> Ben Roberts <benroberts@runtime-collective.com> writes:
> > The scheduled maintenance script throws the following error:
>
> > FATAL 2: open of /2/var/lib/postgres/data/pg_clog/0002 failed: No such file
> > or directory
>
> Could we see the results of ls -l /2/var/lib/postgres/data/pg_clog ?
Yes, sorry. I should have included that with my original mail:
ns1:/2/var/lib/postgres# ls -l /2/var/lib/postgres/data/pg_clog
total 588
-rw------- 1 postgres postgres 262144 Sep 22 01:05 0004
-rw------- 1 postgres postgres 262144 Sep 25 01:05 0005
-rw------- 1 postgres postgres 65536 Sep 25 04:40 0006
Having done some investigation, it now appears to me as if this problem
could possibly stem from having moved the postgres data directory from
/var/lib/postgres to /2/var/lib/postgres. I say this because an ls in the
old directory doesn't look entirely healthy to me:
ns1:/2/var/lib/postgres# ls -l /var/lib/postgres
total 25
-rw-r--r-- 1 postgres postgres 1768 Sep 6 04:39 >g?L&??l?X0[r??R???\
drwx------ 6 postgres postgres 1024 Aug 22 09:29 data.old
-rw-r--r-- 1 postgres postgres 16638 Sep 6 04:28 tfinance.db.lst
-rw-r--r-- 1 postgres postgres 3371 Sep 6 04:39 ?????h???ex??+?Y0e??
It looks as if postgres is using both directories in some way.
thanks for your help,
Ben
