databases/cego: 2.30.7 -> 2.30.11

- Fix in CegoRecoveryManager::recoverTableSet, the lsn was incremented
  which lead to leaks in the transaction log. This could result in
  an incomplete recovery procedure
- Improvements for tableset recovery, external log manage field is
  checked in CegoAdminThread::medRecover before restore procedure is
  started.
- Fix in CegoLogManager::logAction, if online redo log is full, the
  current log entry has to be written anyway, otherwise a checkpoint
  is written and subsequent logAction call in CegoTableManager::logIt
  might lead to duplicate entries in case of a crash recovery
- Fixes for query and table cache added (addEntry method was still not clean)
- Added tableset runstate CHECKPOINT to be set during a tableset
  checkpoint is performed.
  Since this is a critical section in terms of data consistency,
  no system crash should occur while writing a checkpoint.
  If so, the tableset now is marked with status CHECKPOINT and cannot be
  used anymore ( tableset recovery from backup required )
- Patch in CegoDistManager::startTableSet, before starting redo log
  file recovery, the tableset state has to be set to RECOVERY
  Otherwise, occupied redo logs are not archived by the log manager.
  This problem might occur in case of a crash recovery with archive
  mode set to ON
- Patch in CegoQueryCache and CegoTableCache ( for each method addEntry )
  The usedSize calculation was not done correctly for replaces entries
- Added table and cache used size information to show tableset admin command
  This indicates the amount of memory, which is already allocated
  for cached data
- Added synrchonization for query and table cache handling.
  The lack of synchronization might lead to core dumps, if a cache
  entry is freed but also be used by a query
  So before cache cleanup, it has to be checked,
  if the corresponding cache entry is still in use
  If so, it has to be wait, until the cache is clean. For both
  caches ( query and table), the similar logic is used
- Added improvement for query cache handling
  If a stored function, which are used in the cached query, was
  modified, the cache entry will be invalidated
  For this, the CegoSelect::getTableList method was changed to
  CegoSelect::getObjectList and also the used functions are evaluated
  and added to this list.
- Adapted sysmtexp and sysmtimp X-port utilities for current schema definition
- Cache cleanup in CegoQuery class is performed now AFTER the
  modifying action.Otherwise, it may appear, that a cache entry is
  made after cache cleanup but also before the modifying action.
  This may lead to wrong results retrieved from obsolete query cache

Submitted by:	Bjoern Lemke <lemke@lemke-it.com>

2 files changed, 4 insertions, 4 deletions

diff --git a/databases/cego/Makefile b/databases/cego/Makefile
index 7f67255eefdb..b95dadc41f6c 100644
--- a/databases/cego/Makefile
+++ b/databases/cego/Makefile
@@ -1,7 +1,7 @@
 # $FreeBSD$
 
 PORTNAME=	cego
-PORTVERSION=	2.30.7
+PORTVERSION=	2.30.11
 CATEGORIES=	databases
 MASTER_SITES=	http://www.lemke-it.com/
 
diff --git a/databases/cego/distinfo b/databases/cego/distinfo
index 56d7c23ab2b2..5a676ed5d349 100644
--- a/databases/cego/distinfo
+++ b/databases/cego/distinfo
@@ -1,3 +1,3 @@
-TIMESTAMP = 1465626730
-SHA256 (cego-2.30.7.tar.gz) = 13e143c7920e83d8e8f7c759c847832265dba84d8db47d547585aad95de033af
-SIZE (cego-2.30.7.tar.gz) = 1396808
+TIMESTAMP = 1466621042
+SHA256 (cego-2.30.11.tar.gz) = 4cf0c1d7e7d65d1ef33f01b7ccd4df80bee78006699b38cf66a2d409dab071fe
+SIZE (cego-2.30.11.tar.gz) = 1399013