Thread: log shipping from 64 bit linux server to a 32 bit linux server
According to the documentation it's not possible to log ship from a 64 bit server to a 32 bit server.
I just want to confirm that this is the case before I waste a whole lot of time trying to set it up.
I just want to confirm that this is the case before I waste a whole lot of time trying to set it up.
> 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. -- Tatsuo Ishii SRA OSS, Inc. Japan
On Thu, Mar 26, 2009 at 2:05 PM, Tatsuo Ishii <ishii@postgresql.org> wrote:
> According to the documentation it's not possible to log ship from a 64 bitI think the doc is quite correct.
> server to a 32 bit server.
So what is the best way to accomplish a failover from a 64 bit machine to a 32 bit machine?
On Wed, Mar 25, 2009 at 7:08 PM, Tim Uckun <timuckun@gmail.com> wrote: > > On Thu, Mar 26, 2009 at 2:05 PM, Tatsuo Ishii <ishii@postgresql.org> wrote: >> >> > 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?
slony?
That sound more like a question than an answer :)
Can I presume it doesn't care about the architecture of the OS?
> >> > 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. -- Tatsuo Ishii SRA OSS, Inc. Japan
On Wed, Mar 25, 2009 at 8:23 PM, Tatsuo Ishii <ishii@postgresql.org> wrote: >> >> > 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. :)
> >> >> > 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
Tatsuo Ishii wrote: >> > > 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. > Heartbeat does work with 32/64 bit combo. However, CARP is another (simpler) option as well. Additionally, if you were going with that solution, you're likely using a VIP, so adding the complexity of pgpool isn't really required either...for better performance you could use pgBouncer (if you really needed connection pooling). In any case, your HA solution (Heartbeat/CARP) could definitely trigger a slony switchover to minimize downtime, but might end up losing some transactions due to the asynchronous nature of slony. Though, as others have intimated, the best solution out there is for you (if you want synchronous HA) is to get another 64 bit system for your secondary, or even install a 32 bit OS on your 64 bit system, so you have 2 32 bit systems. In which case you'd probably want to add DRBD in to the mix for your active WALs.. -- Chander Ganesan Open Technology Group, Inc. One Copley Parkway, Suite 210 Morrisville, NC 27560 919-463-0999/877-258-8987 http://www.otg-nc.com
On Thu, Mar 26, 2009 at 02:08:33PM +1300, Tim Uckun wrote: > On Thu, Mar 26, 2009 at 2:05 PM, Tatsuo Ishii <ishii@postgresql.org> wrote: > > > 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? What about running a 32bit build of PG on the 64bit machine? -- Sam http://samason.me.uk/
What about running a 32bit build of PG on the 64bit machine?
How would one go about doing something like this?
On Thu, Mar 26, 2009 at 3:32 PM, Tim Uckun <timuckun@gmail.com> wrote: > > >> >> >> What about running a 32bit build of PG on the 64bit machine? > > > How would one go about doing something like this? Compiling with the proper -march flags I believe. It's been like 5 years since I had to mess with such things, so google it a bit first.
On Fri, Mar 27, 2009 at 10:32:33AM +1300, Tim Uckun wrote: > > What about running a 32bit build of PG on the 64bit machine? > > How would one go about doing something like this? Depending on your distribution you should be able to install 32bit binaries alongside 64bit binaries; for example in Debian you can do: http://www.unixtutorial.org/2008/03/install-32-bit-deb-packages-on-64-bit/ Alternatives would be to build the code yourself as Scott said, or to copy the binaries across from your 32bit system. Assuming you did the latter you'd need to make sure you got all the appropriate libraries as well which may be a bit of a fiddle---especially to keep up to date. Then again, if you're building it yourself you'd need all the libraries anyway so you may as well figure out how to get 32bit packages installed in your 64bit system anyway. -- Sam http://samason.me.uk/