From: | Randall Smith <randall(at)tnr(dot)cc> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: oracle synchronization strategy |
Date: | 2004-11-02 03:53:14 |
Message-ID: | DwDhd.19630$0j.4423@lakeread07 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Joachim,
The mirror only has to go from oracle to pgsql and the schema/tables
never change. I'm going to take a look at dbmirror. Thanks for the advice.
Randall
Joachim Wieland wrote:
> Hi Randall,
>
> On Sun, Oct 31, 2004 at 11:25:46PM -0600, Randall Smith wrote:
>
>>1. Set up stored proc on oracle that records a INSERT, UPDATE, DELETE
>>SQL action taken on a table into a log table.
>>2. Program reads the log table on oracle and issues the same SQL command
>>on the postgres db. In the same transaction, postgres writes to a log
>>showing the command has been executed.
>>3. The program will query the oracle log table on some frequency ~30
>>seconds.
>
>
> It depends on what you're trying to achieve.
>
> Your way might work if you only want to mirror oracle -> pgsql but not vice
> versa.
>
> Furthermore you need to do manual maintenance on the pgsql side if you
> change your schema on the oracle side (create/drop/change tables, ...)
>
> I've done something similar with MS SQL -> pgsql and perl some years ago.
> Shout if you're interested.
>
> There's also dbmirror in contrib/ that works in a similar way.
>
>
> Joachim
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joolz | 2004-11-02 06:33:04 | Re: unique problem |
Previous Message | Tom Lane | 2004-11-02 03:44:42 | Re: deadlock with vacuum full on 7.4.5 |