Hi, In a fb-support discussion it has occurred to me and Karol Bieniaszewski that the old shadow file feature is actually useful for some purposes.
Karol runs the master on a RAM disk to make sure reads and searches are as fast as possible, and has a shadow file on a regular disk to protect against data loss on power failures. We will soon have a somewhat similar setup. So, I ask you in the devel team: is the shadow file feature going to go away or will you make sure it stays functional? If it will be removed, what would you say is a viable alternative to achieve the same thing with a RAM disk + regular disk combo? Is replication a viable option? Perhaps even better? Why? Pros & cons? I can imagine that the shadow file technology will incur regular disk latencies on all writes (including header updates for read only transaction), while replication would allow updates to "return" after updating only the RAM master and read only transactions would only touch the RAM disk header - thay wouldn't be replicated at all. So, what would be the downsides of replication as opposed to shadow file? Higher risk of data loss? If so, how/why? What else? Regards, Kjell -- -------------------------------------- Kjell Rilbe DataDIA AB E-post: kj...@datadia.se Telefon: 08-761 06 55 Mobil: 0733-44 24 64 ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
