Hi, In a Zope / Zeo configuration (2.7.6), is there a way, on the Zope instance, to know when the database (Zeo) was last packed ? Thanks. Pascal ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pascal Peregrina wrote:
In a Zope / Zeo configuration (2.7.6), is there a way, on the Zope instance, to know when the database (Zeo) was last packed ?
Thanks.
Repozo knows this for the underlying FileStorage: http://www.zope.org/Wikis/ZODB/FileStorageBackup AFAIK, there is no wire-protocol-level way to check for it in the ZEOClientStorage. BTW, this question would get better-informed response on the zodb-dev list (which I have CC'ed). Tres. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCggzv+gerLs4ltQ4RAqkUAJ46baO6FeV2mKXpd9CQq7c7pvSSugCcDkU0 OJyFipH9BLTmy1mc31kb1to= =4W8m -----END PGP SIGNATURE-----
Pascal Peregrina wrote:
In a Zope / Zeo configuration (2.7.6), is there a way, on the Zope instance, to know when the database (Zeo) was last packed ?
Publicly, maybe not, but there'll definitely be away to find it out since the pack machinery checks this. zodb-dev@zope.org may be the place to ask... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
[Pascal Peregrina]
In a Zope / Zeo configuration (2.7.6), is there a way, on the Zope instance, to know when the database (Zeo) was last packed ?
[Chris Withers]
Publicly, maybe not, but there'll definitely be away to find it out since the pack machinery checks this.
Sorry, pack times aren't recorded anywhere, period. In a FileStorage, each transaction record has a status byte, and that byte is set to a special "this transaction was packed" value the first time the transaction is in fact packed. That's how "the packing machinery" knows whether it's been asked to pack a transaction that's already been packed. The packing machinery has no idea _when_ a transaction was packed, it knows only whether a given transaction _has_ been packed. I suppose you could write a script to rummage through a Data.fs file, searching for the transaction with the largest tid that has been packed, or search for the transaction with the smallest tid that hasn't been packed. tids normally bear a close relationship to wall-clock time, but that's not necessarily true either.
participants (4)
-
Chris Withers -
Pascal Peregrina -
Tim Peters -
Tres Seaver