Обсуждение: : Postgresql Error after recovery
DISCLAIMER: Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and delete this e-mail , whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Ver sé Innovation Pvt Ltd.
\postgres=# \c oltp_dbFATAL: index "pg_attribute_relid_attnum_index" contains unexpected zero page at block 0HINT: Please REINDEX it.Previous connection keptCan anyone please help us.
\postgres=# \c oltp_dbFATAL: index "pg_attribute_relid_attnum_index" contains unexpected zero page at block 0HINT: Please REINDEX it.Previous connection keptCan anyone please help us.You have HINT given to REINDEX it. Use reindexdb from OS.
On Wed, Jul 4, 2012 at 2:11 PM, Raghavendra <raghavendra.rao@enterprisedb.com> wrote:\postgres=# \c oltp_dbFATAL: index "pg_attribute_relid_attnum_index" contains unexpected zero page at block 0HINT: Please REINDEX it.Previous connection keptCan anyone please help us.You have HINT given to REINDEX it. Use reindexdb from OS.
DISCLAIMER: Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and delete this e-mail , whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Ver sé Innovation Pvt Ltd.
Re-index option did not work.
Single user mode option did not work as well -[postgres@localhost bin]$ postgres --single oltp_db -E -D /usr/local/postgresql-9.0.1/data2012-07-04 04:30:47 CDT [26072]: [1-1] user=,db= FATAL: index "pg_attribute_relid_attnum_index" contains unexpected zero page at block 02012-07-04 04:30:47 CDT [26072]: [2-1] user=,db= HINT: Please REINDEX it.Last option would be dump and restore. We need to avoid that reduce the downtime.
Re-index option did not work.Single user mode option did not work as well -[postgres@localhost bin]$ postgres --single oltp_db -E -D /usr/local/postgresql-9.0.1/data2012-07-04 04:30:47 CDT [26072]: [1-1] user=,db= FATAL: index "pg_attribute_relid_attnum_index" contains unexpected zero page at block 02012-07-04 04:30:47 CDT [26072]: [2-1] user=,db= HINT: Please REINDEX it.Last option would be dump and restore. We need to avoid that reduce the downtime.How about starting the instance with ignore_system_indexes=true ? And do dump & restore. Am not sure on this procedure. Should someone here would have better idea on this.
DISCLAIMER: Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and delete this e-mail , whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Ver sé Innovation Pvt Ltd.