Thread: Unable to access records in table!

Hello guys,

I have a problem when launching a query on a table:

When I submit: SELECT COUNT(*) FROM billing;
the output is this:


FATAL 2:  open of /pgdata/pg_clog/0353 failed: No such file or directory
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: NOTICE:
Message from PostgreSQL backend:
        The Postmaster has informed me that some other backend
        died abnormally and possibly corrupted shared memory.
        I have rolled back the current transaction and am
        going to terminate your database system connection and exit.
        Please reconnect to the database system and repeat your query.
Failed.

Indeed /pgdata/pg_clog/0353 isn't there!
Yesterday the file had a different name... It seems that every day a mew
file is created...
Does anyone of you knows what this means?

Thanx!

Wim

> -----Original Message-----
> From: Wim [mailto:wdh@belbone.be]
>
> Hello guys,
>
> I have a problem when launching a query on a table:
>
> When I submit: SELECT COUNT(*) FROM billing;
> the output is this:
>
>
> FATAL 2:  open of /pgdata/pg_clog/0353 failed: No such file
> or directory
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: NOTICE: 
> Message from PostgreSQL backend:
>         The Postmaster has informed me that some other backend
>         died abnormally and possibly corrupted shared memory.
>         I have rolled back the current transaction and am
>         going to terminate your database system connection and exit.
>         Please reconnect to the database system and repeat your query.
> Failed.
>
> Indeed /pgdata/pg_clog/0353 isn't there!
> Yesterday the file had a different name... It seems that
> every day a mew
> file is created...
> Does anyone of you knows what this means?
>
> Thanx!
>
> Wim
>
Are the files actually there?
pg_clog contains, i believe, the transaction commit log.
If this is missing this could be bad.
I must admit that I would expect errors on other queries than just
this one if you were missing your commit log.
This is the limit of my knowledge sorry.
Try asking on pgsql-general and, if no joy there, pgsql-hackers.
Include details of postgresql version and OS.
Regards,
- Stuart