Re: Strategy for moving a large DB to another machine with least possible down-time - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Strategy for moving a large DB to another machine with least possible down-time
Date
Msg-id 541ED710.6060607@aklaver.com
Whole thread Raw
In response to Re: Strategy for moving a large DB to another machine with least possible down-time  (Andreas Joseph Krogh <andreas@visena.com>)
Responses Re: Strategy for moving a large DB to another machine with least possible down-time  (Andreas Joseph Krogh <andreas@visena.com>)
List pgsql-general
On 09/21/2014 05:44 AM, Andreas Joseph Krogh wrote:
> På søndag 21. september 2014 kl. 13:51:00, skrev Bill Moran
> <wmoran@potentialtech.com <mailto:wmoran@potentialtech.com>>:
>

>
> I see this limitation in Slyny:
> http://slony.info/documentation/2.2/limitations.html
>
> Slony-I does not automatically replicate
>
>   *
>
>     Changes to large objects (BLOBS)
>
>   *
>
>     Changes made by DDL commands
>
>   *
>
>     Changes to users and roles
>
> Not being able to replicate BLOBS is a show-stopper for me as we have
> lots of them.

Well I would say it depends on where you are storing the binary data, in
large objects or in a bytea column?  If you are using bytea columns then
you would be okay. If it is large objects then you have a problem.

> Seems PITR is my only option?
> --
> *Andreas Joseph Krogh*


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Andreas Joseph Krogh
Date:
Subject: Re: Strategy for moving a large DB to another machine with least possible down-time
Next
From: Andreas Joseph Krogh
Date:
Subject: Re: Strategy for moving a large DB to another machine with least possible down-time