Dear community,
for some reason the post I sent yesterday night still did not show up on
the mailing lists. I have set up some links on the developers side under
http://developer.postgresql.org/~wieck/slony1.html
The concept will be the base for some of my work as a Software Engineer
here at Af
On Nov 11, 2003, at 12:11 PM, Joe Conway wrote:
Jan Wieck wrote:
http://developer.postgresql.org/~wieck/slony1.html
Very interesting read. Nice work!
Ditto. I'll read it a bit closer later, but after a quick read it
seems quite complete and well thought out. I especially like
that sequences are
Jan Wieck wrote:
http://developer.postgresql.org/~wieck/slony1.html
Very interesting read. Nice work!
We want to build this system as a community project. The plan was from
the beginning to release the product under the BSD license. And we think
it is best to start it as such and to ask for sugges
Joe Conway wrote:
Jan Wieck wrote:
http://developer.postgresql.org/~wieck/slony1.html
Very interesting read. Nice work!
We want to build this system as a community project. The plan was from
the beginning to release the product under the BSD license. And we think
it is best to start it as such an
Jan Wieck wrote:
If you mean to configure the system to replicate rows to different
destinations (slaves) based on arbitrary qualifications, no. I had
thought about it, but it does not really fit into the "datacenter and
failover" picture, so it is not required to meet the goals and adds
unnece
Christopher Browne wrote:
In the last exciting episode, [EMAIL PROTECTED] (Jan Wieck) wrote:
I look forward to your comments.
It is not evident from the paper what approach is taken to dealing
with the duplicate key conflicts.
The example:
UPDATE table SET col1 = 'temp' where col = 'A';
UPDAT
In the last exciting episode, [EMAIL PROTECTED] (Jan Wieck) wrote:
> I look forward to your comments.
It is not evident from the paper what approach is taken to dealing
with the duplicate key conflicts.
The example:
UPDATE table SET col1 = 'temp' where col = 'A';
UPDATE table SET col1 = 'A'
On Tue, Nov 11, 2003 at 03:38:53PM -0500, Christopher Browne wrote:
> In the last exciting episode, [EMAIL PROTECTED] (Jan Wieck) wrote:
> > I look forward to your comments.
>
> It is not evident from the paper what approach is taken to dealing
> with the duplicate key conflicts.
>
> The example:
