how do you deal with the lack of a serious solution for replication / hot standby? Why is this not a more pressing issue for the postgresql developers? I went

how do you deal with the lack of a serious solution for replication / hot standby? Why is this not a more pressing issue for the postgresql developers? I went to the SF Postgres meetup a month or two ago where they talked about new features in 8.4. Josh Berkus, one of the core devs hosts the meetup. Anyhoo, hot standby _is_ a huge issue for them. We talked about it for 20 minutes. They had a dev who worked his tail off on the issue for several months. There was a lot of hope that hot standby was going to make it into the 8.4 release, but there were a few too many bugs on corner cases for them to ship the feature in 8.4 without a big refactor. Postgres core is very concerned about replication, but shipping a stable product is their biggest concern. So, good news is that hot standby is a big priority for 8.5. Bad news, is the release isn't slated until next year.