On 10/7/07, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > "Faber J. Fedor" <faber@xxxxxxxxxxx> writes: > > I've been given the job of creating a hot/warm backup server > > for a live Postgresql server. The problem is two-fold: 1) it's version > > 7.4.9 and an upgrade is not feasible at this time and b) there are > > multiple instances of postgresql running on the box; not multiple > > databases, multiple *servers*, each listening on a different port (it > > was a business requirement from what I've been told). > > If they won't let you update to 7.4.18 (the current release in that > branch), you would be best advised to resign at once, before you get > blamed for the train wreck that is inevitably in this system's future. > 7.4.9 is two years old, and I count at least six fixes since then for > data-loss bugs of the *will*-bite-you-eventually type; plus a couple > more that you might be at risk for depending on which features you use. I agree. Although I'd set up your new job first if possible. I also agree that Slony is your best bet. Note only the older versions of slony run on 7.4, so make sure you download the version of slony that works with 7.4. I think it's 1.0, could be 1.1 or so. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
