| From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
|---|---|
| To: | Venkat Balaji <venkat(dot)balaji(at)verse(dot)in> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: : Postgresql Error after recovery |
| Date: | 2012-07-04 10:05:53 |
| Message-ID: | CA+h6AhjcuOxHvJ7OxArMi=zDj+ciNwWkumXgk4aj6LS7gzRjVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> Re-index option did not work.
>
> Single user mode option did not work as well -
>
> [postgres(at)localhost bin]$ postgres --single oltp_db -E -D
> /usr/local/postgresql-9.0.1/data
> 2012-07-04 04:30:47 CDT [26072]: [1-1] user=,db= FATAL: index
> "pg_attribute_relid_attnum_index" contains unexpected zero page at block 0
> 2012-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.
http://www.postgresql.org/docs/9.0/interactive/runtime-config-developer.html
---
Regards,
Raghavendra
EnterpriseDB Corporation
Blog: http://raghavt.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkat Balaji | 2012-07-04 10:29:39 | Re: : Postgresql Error after recovery |
| Previous Message | Venkat Balaji | 2012-07-04 09:46:39 | Re: : Postgresql Error after recovery |