Re: [GENERAL] Postmaster cannot start

2006-05-16 Thread Chun Yit\(Chronos\)
doubt on my mind. Regards Beh - Original Message - From: Tom Lane [EMAIL PROTECTED] To: Chun Yit(Chronos) [EMAIL PROTECTED] Cc: pgsql-general@postgresql.org Sent: Tuesday, May 16, 2006 1:03 PM Subject: Re: [GENERAL] Postmaster cannot start Chun Yit\(Chronos\) [EMAIL PROTECTED

[GENERAL] Postmaster cannot start

2006-05-15 Thread Chun Yit\(Chronos\)
Hi, my postgresql version 7.4.5 cannot start until this morning, when i check the log file, it give me this error this is part of my log file DEBUG: vacuuming "pg_catalog.pg_class"DEBUG: "pg_class": found 9823 removable, 1017 nonremovable row versions in 205 pagesDETAIL: 0 dead row

Re: [GENERAL] Postmaster cannot start

2006-05-15 Thread Chun Yit\(Chronos\)
4) how can i solve this problem? The base table pg_class should be ok(pg_class_oid_ind indicates both have the same cardinality). Try to reindex pg_class as the superuser. but not i not be able to reindex the table because i cannot start the postmaster. postmaster give me error every time

Re: [GENERAL] Postmaster cannot start

2006-05-15 Thread Chun Yit\(Chronos\)
Qingqing Zhou [EMAIL PROTECTED] writes: But not sure why it reports the following error message (which looks like a post-commit cleanup caused error): DEBUG: AbortCurrentTransaction PANIC: cannot abort transaction 14135438, it was already committed I think this is an artifact of

Re: [GENERAL] catalog is missing 16 attribute(s) for relid 8202590

2006-05-09 Thread Chun Yit\(Chronos\)
? cause it just temporary table, can i just remove from database? Regards Beh - Original Message - From: Tom Lane [EMAIL PROTECTED] To: Chun Yit(Chronos) [EMAIL PROTECTED] Cc: pgsql-general@postgresql.org Sent: Monday, May 08, 2006 10:43 PM Subject: Re: [GENERAL] catalog is missing 16

[GENERAL] catalog is missing 16 attribute(s) for relid 8202590

2006-05-08 Thread Chun Yit\(Chronos\)
hello, i found this ERROR msg at our postgresql log file at one of my client. what i did is i 1) kill -9 (postmaster process id). 2) remove the postmaster.pid file under /usr/local/pgsql/data/ 3) restart the postmaster process. then no more error msg in the postgresql log file. problem