Re: oracle synchronization strategy

From: Joachim Wieland <joe(at)mcknight(dot)de>
To: Randall Smith <randall(at)tnr(dot)cc>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: oracle synchronization strategy
Date: 2004-11-01 11:04:01
Message-ID: 20041101110401.GA24444@mcknight.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Garamond 2004-11-01 12:58:06 AT TIME ZONE: "convert"?
Previous Message Ian Barwick 2004-11-01 10:05:09 Re: Max length name of a database/schema