Hello Liu, MaxDB's savepoint is similar to Oracle's checkpoint.
If no other reason caused a savepoint a savepoint is written if since the last savepoint 2/3 of the logvolume is used. If no other reason caused a savepoint and 5000 Log writes were done in at least 600 sec (default) a sapoint is triggered. Kind regards, Uwe >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Monday, April 18, 2005 1:30 PM >To: [email protected] >Subject: a doubt of savepoint > > In maxdb help,there is a part of savepoint document: > > As savepoints affect system performance, the database >system does not >perform a new savepoint automatically at the end of this time >interval. It >waits for 5,000 I/O operations and only then does it check how >much time >has elapsed since the last savepoint. This means that the >system does not >write a savepoint unless at least 5,000 I/O operations have >taken place >since the last savepoint. With a lower number of I/O >operations, more time >may elapse until the next savepoint. > > And the "_Restart_time" is 600 sec! > > Too long to active database writer and log writer. > > In oracle,there is a concept named "checkpoint".I don't >know whether >"chechpoint = savepoint" > > thank! > >_________________________________________________________________ >与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn > > >-- >MaxDB Discussion Mailing List >For list archives: http://lists.mysql.com/maxdb >To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
