Re: [ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-31 Thread Tomasz Chmielewski
) whatever command I send to postgres, should I expect Could not open file pg_clog/05DC: No such file or directory? If so, it should be documented, and a way to recover from such a situation should be explained. 2) is pgpool behaviour correct? -- Tomasz Chmielewski http://wpkg.org -- Sent via pgsql

Re: [ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-30 Thread Tomasz Chmielewski
On 07.05.2011 23:19, Tomasz Chmielewski wrote: On 06.05.2011 10:42, Tomasz Chmielewski wrote: bookstor=# SELECT 1 FROM core_wot_seq FOR UPDATE; ERROR: could not access status of transaction 1573786613 DETAIL: Could not open file pg_clog/05DC: No such file or directory. How do I best recover

Re: [ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-07 Thread Tomasz Chmielewski
On 06.05.2011 10:42, Tomasz Chmielewski wrote: On 04.05.2011 22:27, Tomasz Chmielewski wrote: Then another pg_clog file disappeared. OK, I have: bookstor=# SELECT * FROM core_wot_seq; sequence_name | last_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled

Re: [ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-06 Thread Tomasz Chmielewski
On 04.05.2011 22:27, Tomasz Chmielewski wrote: Then another pg_clog file disappeared. OK, I have: bookstor=# SELECT * FROM core_wot_seq; sequence_name | last_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called

[ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-04 Thread Tomasz Chmielewski
corrupted due to a server crash - this server never crashed How should I continue from that (assuming I can't reliably verify if something wrong is going with the hardware or not - points 4 and 5)? -- Tomasz Chmielewski http://wpkg.org -- Sent via pgsql-admin mailing list (pgsql-admin

Re: [ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-04 Thread Tomasz Chmielewski
. Assuming we can't determine what caused the corruption (bitflip, kernel bug, bad RAM, postgres bug, silent HDD error etc.) - how should I best recover from this? -- Tomasz Chmielewski http://wpkg.org -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your

Re: [ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-04 Thread Tomasz Chmielewski
or directory. I can't exclude some corruption happened much earlier on db10; the whole database (as binary files) was copied to db20 almost 2 months ago. Why would it start showing pg_clog files missing just 2 days ago, and not earlier? Hmm. -- Tomasz Chmielewski http://wpkg.org -- Sent via pgsql

Re: [ADMIN] 'SGT DETAIL: Could not open file pg_clog/05DC: No such file or directory' - what to do now?

2011-05-04 Thread Tomasz Chmielewski
On 04.05.2011 22:13, Tomasz Chmielewski wrote: On 04.05.2011 21:50, Scott Marlowe wrote: Then another pg_clog file disappeared. OK, I have: bookstor=# SELECT * FROM core_wot_seq; sequence_name | last_value | increment_by | max_value | min_value | cache_value | log_cnt