| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Andreas Joseph Krogh <andreas(at)visena(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Strategy for moving a large DB to another machine with least possible down-time |
| Date: | 2014-09-21 13:48:00 |
| Message-ID: | 541ED710.6060607@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)potentialtech(dot)com <mailto:wmoran(at)potentialtech(dot)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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2014-09-21 13:50:59 | Re: Strategy for moving a large DB to another machine with least possible down-time |
| Previous Message | Andreas Joseph Krogh | 2014-09-21 12:44:06 | Re: Strategy for moving a large DB to another machine with least possible down-time |