Hot Standby won't work with hash indexes because they are non-recoverable. We have a number of ways of dealing with this:
1. Workaround: Implement WAL for hash indexes 2. Specific Solution: make hashcostestimate() massively increase cost of scans during recovery so that they will very seldom be picked and make hashbeginscan() refuse scans during recovery in case they do happen 3. Generic Solution: add amisrecoverable flag to pg_am, and alter generic index AM to check whether index is recoverable before selecting it during planning I was hoping to do (1), but I'm looking for a quicker solution now so we can tie up loose ends for review. (2) seems most appropriate, since it will last only until (1) is complete in a later release. Anyone see additional options or prefer alternatives? -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
