Tomasz Chmielewski <mangoo@xxxxxxxx> wrote: > On 1st May, I saw this message in my postgres log: > > May 2 06:52:02 db10 postgres[3590]: [29829-1] 2011-05-02 06:52:02 > SGT ERROR: could not access status of transaction 1573786613 > May 2 06:52:02 db10 postgres[3590]: [29829-2] 2011-05-02 06:52:02 > SGT DETAIL: Could not open file "pg_clog/05DC": No such file or > directory. > May 2 06:52:02 db10 postgres[3590]: [29829-3] 2011-05-02 06:52:02 > SGT STATEMENT: SELECT 1 FROM core_bill_id_seq FOR UPDATE You saw errors on the 1st dated for the 2nd? > Now, I'm not sure what I should do about it. Database behaves > "funny", some inserts do not work. Define "funny". What happens when you attempt the inserts which don't work. (Copy and paste any error messages.) Is it all tables? All inserts to one table? Any other discernible pattern? > 4) I may have hardware problems - but this server is running for > almost 1 year now, is super stable - servers with hardware issues > are likely to show some issues as well Does the server have ECC memory? Do you have SMART monitoring of the storage system, or something similar? Any errors showing in any system logs? -Kevin -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
