Thomas Antepoth wrote:
>
> Michael,
>
> As Dustin pointed out, he solved it by merging a unique database
> id with a sequence into a unique primary key.
> If the newly inserted record gets the database id of database 2
> it will later not be recognized belonging to the relation by a
> "... wh
Thomas Antepoth wrote:
>
> But what to do, if there are several local masters?
I may have interpreted the problem incorrectly, but here is
a similar problem I had...
Say I have 5 plants in a large company. Each of these
plants has a variety of machinery and tools which have
detailed maintance
Michael,
On Wed, 17 Feb 1999, Michael Davis wrote:
> I was thinking about creating a trigger on every table that would write an
> insert, update, or delete statement into a log file. Each replicated
> database would pro-actively read these and post them.
Right. This is one of the prerequesites
]]
Sent: Monday, February 15, 1999 9:16 PM
To: [EMAIL PROTECTED]
Subject:Re: [GENERAL] Replication of databases (esp.
postgres)
Dustin,
thank you for your answer.
On Mon, 15 Feb 1999, dustin sallings wrote:
> // {Replication of
