[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: backend requirements for syncrepl

Jong-Hyuk wrote:

How about having the entryCSN as the max TIMESTAMP values of all the
relevant table rows for an entry ? At the next synchronization time, it
would be possible to send only those entries having any of the relevant
TIMESTAMP values greater than the synchronization cookie.

Sure.  The point is that these are (RDBMS dependent, BTW) details
which can be arranged later (depending on whether the overload
due to reloads is an issue or not, which also depends on the scenario).
The first issue is to have syncrepl working with a producer that is not
syncrepl-aware (e.g. doesn't recognize the control).


   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497