| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | scott(dot)marlowe(at)gmail(dot)com |
| Cc: | ishii(at)postgresql(dot)org, timuckun(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: log shipping from 64 bit linux server to a 32 bit linux server |
| Date: | 2009-03-26 02:45:10 |
| Message-ID: | 20090326.114510.48694762.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> >> >> > According to the documentation it's not possible to log ship from a 64
> >> >> > bit
> >> >> > server to a 32 bit server.
> >> >>
> >> >> I think the doc is quite correct.
> >> >
> >> >
> >> > So what is the best way to accomplish a failover from a 64 bit machine to a
> >> > 32 bit machine?
> >>
> >> slony?
> >
> > IMO Slony doesn't do failover.
>
> Not all by itself. But then neither does PITR by itself. But I'm sure
> you know that. :)
I know what you think:-)
Problem is, he asks high availabilty, that means, no SPOF, minimum
down time. For the purpose, I suppose pgpool-HA(actually
heartbeat)+pgpool-II+Slony-I might work, but I'm not sure heartbeat
does work with 32/64bit combo.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Duffey | 2009-03-26 04:05:03 | Re: could not access status of transaction |
| Previous Message | Scott Marlowe | 2009-03-26 02:40:21 | Re: log shipping from 64 bit linux server to a 32 bit linux server |