Tag Info

New answers tagged

1

I just ran into the same issue on Postgres 8.3.11. Although I could not identify the root cause, the fix was simple enough: REINDEX INDEX tbl_cust_id_idx; This page contains hints as to what may have caused the error, although they are vague: An indicated table index was corrupted (may be a result of recent postgres or system failure, there was a lack ...


2

If the PostgreSQL version and architecture is the same on the target so they're binary compatible: Set up streaming replication with WAL archive fallback, so the new host replicates from the old one. Enable hot_standby mode so you can connect to the new host read-only. Test. Then when you're ready to cut over, stop the old server and pg_ctl promote the new ...



Top 50 recent answers are included