On Fri, Jan 24, 2003 at 11:15:30AM +0800, Ariz Jacinto wrote: > > in our machine-setup, rollback-ed transactions doesn't matter. > we are only going to replicate those sql queries that have been committed, > coz it wont be logged on the server anyway if it wasnt committed or > erroneous.
Sounds like rserv to me. But rserv doesn't replicate sql queries; it replicates data (incremental). I think this is a good choice because rserv doesn't have to worry about what sql to filter (e.g. LOCK, DROP, CREATE, ALTER). It is also a faster approach. When the slave requests for an update the master generates a COPY-able file of all the INSERT-ed records. Imagine how would the slave benefit in performance by just issuing only one COPY instead of multiple INSERT sqls. pgsql.com just released[1] its commercial replication solution (eRServer v1.2) last December. You might be interested. :-) [1] http://www.pgsql.com/press/PR_eRServer1_2.html HTH -- $_=q:; # SHERWIN # 70;72;69;6e;74;20; 27;4a;75;73;74;20; 61;6e;6f;74;68;65; 72;20;50;65;72;6c; 20;6e;6f;76;69;63; 65;27;:;;s=~?(..); ?=pack q$C$,hex$1; ;;;=egg;;;;eval;;; _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
