[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] bi-directional syncing help request
From:       Bèrto ëd Sèra <berto.d.sera () gmail ! com>
Date:       2013-08-09 15:38:05
Message-ID: CAKwGa__AWC6tGxPJheMMm-Xst25rfb_H6_ZSJGgshK3T8H1p0w () mail ! gmail ! com
[Download RAW message or body]

>A pg_dump from one system or the other will effectively overwrite the
database it is restored to, so any changes in one system or the other will
be lost
yes, as said, the pre-condition is that she is the one and only possible
data producer.


On 9 August 2013 16:24, bricklen <bricklen@gmail.com> wrote:

> On Fri, Aug 9, 2013 at 8:12 AM, Bèrto ëd Sèra <berto.d.sera@gmail.com>wrote:
>
>> or you can just take a full dump from one box and import it on the other
>> any time you switch. If it's not a big db it should probably be quicker
>> than any alternative approach.
>>
>
> A pg_dump from one system or the other will effectively overwrite the
> database it is restored to, so any changes in one system or the other will
> be lost unless processes are put in place to move that data to a staging
> area before the reload.
> The issue here is that it is a data and structure synchronization problem,
> which isn't something solved very easily using Postgresql's core tools.
> Synchronizing the data using Bash/Python, FDW's etc is reasonably
> straightforward, but synchronizing the DDL changes will require some care.
>
>
>


-- 
==============================
If Pac-Man had affected us as kids, we'd all be running around in a
darkened room munching pills and listening to repetitive music.

[Attachment #3 (text/html)]

<div dir="ltr">&gt;<span \
style="font-family:arial,sans-serif;font-size:12.800000190734863px">A pg_dump from \
one system or the other will effectively overwrite the database it is restored to, so \
any changes in one system or the other will be lost  <br> yes, as said, the \
pre-condition is that she is the one and only possible data \
producer.</span></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 9 \
August 2013 16:24, bricklen <span dir="ltr">&lt;<a href="mailto:bricklen@gmail.com" \
target="_blank">bricklen@gmail.com</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div \
class="gmail_quote"><div class="im">On Fri, Aug 9, 2013 at 8:12 AM, Bèrto ëd Sèra \
<span dir="ltr">&lt;<a href="mailto:berto.d.sera@gmail.com" \
target="_blank">berto.d.sera@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">or you can just take a full dump from one box \
and import it on the other any time you switch. If it&#39;s not a big db it should \
probably be quicker than any alternative approach.</div>

</blockquote><div><br></div></div><div>A pg_dump from one system or the other will \
effectively overwrite the database it is restored to, so any changes in one system or \
the other will be lost unless processes are put in place to move that data to a \
staging area before the reload.<br>

The issue here is that it is a data and structure synchronization problem, which \
isn&#39;t something solved very easily using Postgresql&#39;s core tools.   \
Synchronizing the data using Bash/Python, FDW&#39;s etc is reasonably \
straightforward, but synchronizing the DDL changes will require some care.<br>

<br><br></div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- \
<br>==============================<br><span \
style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:12px;line-height:17px">If \
Pac-Man had affected us as kids, we&#39;d all be running around in a darkened room \
munching pills and listening to repetitive music.</span> </div>



[prev in list] [next in list] [prev in thread] [next in thread]