Den 2012-01-03 21:59 skrev Ann Harrison såhär: > On Tue, Jan 3, 2012 at 3:06 PM, Dmitry Yemanov<firebi...@yandex.ru> wrote: > >> In the past, I liked the idea to wrap the txn IDs, but now I'm more and >> more keen to consider other solutions instead. >> > Completely agree - including having changed my mind. I agree with > Dimitry S. that his replicate/backup/restore/reverse strategy works, > assuming that the load is light enough that the newly restored > replicant can eventually catch up. At the same time, one of > Firebird's strong points is the limited amount of expertise necessary > to manage the system, so in the longer run, either a variable length > transaction id or a record version by record version flag indicating > the size of the transaction id has a lot of merit.
Or a more automated and built-in support to do such a replicate/backup/restore/reverse. For me it's question of time. Sure, I could learn how to setup a cluster and replication. But there are dozens of other things I also need to do yesterday, so having to learn this on top of everything else is a stumbling block. Could the procedure be "packaged" into some kind of utility program or something? I'm thinking that nbackup locks the master file while keeping track of changed pages in a separate file. Perhaps a transaction id consolidation similar to what happens on backup/restore could be performed on a locked database master while logging updates in a separate file, and then bring the consolidated master up to date again. If this is very difficult, perhaps there's no point - devel resources better spent elsewhere. But if it would be a fairly simple task...? Kjell -- -------------------------------------- Kjell Rilbe DataDIA AB E-post: kj...@datadia.se Telefon: 08-761 06 55 Mobil: 0733-44 24 64 ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
