From: | james <james(at)mansionfamily(dot)plus(dot)com> |
---|---|
To: | Jim Nasby <jim(at)nasby(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fake async rep target |
Date: | 2012-05-30 20:28:43 |
Message-ID: | 4FC682FB.3030908@mansionfamily.plus.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Well, I was assuming that there was some intelligence in the receiver
that could effectively parse this for the application; are you
suggesting that is effectively binary deltas to apply to raw pages?
Certainly, Sybase rep server works by creating function calls or SQL
updates (depending on how you set it all up), and a fairly simple parser
can be used to process the received stream.
I was hoping that the receiver code could be used to at least identify
which tuples are affected and their before/after primary keys.
Ideally the result would be a packet by transaction, listing the
impacted tables and for each table a list of affected primary keys and
whether they were inserted, deleted or updated.
James
From | Date | Subject | |
---|---|---|---|
Next Message | james | 2012-05-30 20:32:39 | Re: Fake async rep target |
Previous Message | Robert Haas | 2012-05-30 20:26:09 | Re: Advisory locks seem rather broken |