Skip site navigation (1) Skip section navigation (2)

Re: logical changeset generation v3 - comparison to Postgres-R change set format

From: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
To: Markus Wanner <markus(at)bluegap(dot)ch>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: logical changeset generation v3 - comparison to Postgres-R change set format
Date: 2012-11-17 13:30:27
Message-ID: 50A79173.4@2ndQuadrant.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 11/16/2012 02:46 PM, Markus Wanner wrote:
> Andres,
>
> On 11/15/2012 01:27 AM, Andres Freund wrote:
>> In response to this you will soon find the 14 patches that currently
>> implement $subject.
> Congratulations on that piece of work.
>
>
> I'd like to provide a comparison of the proposed change set format to
> the one used in Postgres-R. I hope for this comparison to shed some
> light on the similarities and differences of the two projects. As the
> author of Postgres-R, I'm obviously biased, but I try to be as neutral
> as I can.
...
> Let's compare by example:
>
>> table "replication_example": INSERT: id[int4]:1 somedata[int4]:1 text[varchar]:1
>> table "replication_example": UPDATE: id[int4]:1 somedata[int4]:-1 text[varchar]:1
>> table "replication_example": DELETE (pkey): id[int4]:1
> In Postgres-R, the change sets for these same operations would carry the
> following information, in a binary representation:
>
>> table "replication_example": INSERT: VALUES (1, 1, '1')
>> table "replication_example": UPDATE: PKEY(1) COID(77) MODS('nyn') VALUES(-1)
>> table "replication_example": DELETE: PKEY(1) COID(78)
Is it possible to replicate UPDATEs and DELETEs without a primary key in 
PostgreSQL-R


Hannu


In response to

Responses

pgsql-hackers by date

Next:From: Markus WannerDate: 2012-11-17 14:00:10
Subject: Re: logical changeset generation v3 - comparison to Postgres-R change set format
Previous:From: Amit KapilaDate: 2012-11-17 13:28:46
Subject: Re: another idea for changing global configuration settings from SQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group