postgresql-9.0.x was declared EoL in September 2015.
Summary:
Remove 9.0 from the list of postgresql versions available in ports
Disconnect postgresql90 ports from the build
Remove postgresql90-pgtcl port
Remove postgresql90-client port
Move the master postgreslXY-plperl makefile to postgresql95-plperl/Makefile.
Adjust include lines in other postgresqlXY-plperl ports
Delete postgresql90-plperl
Move the master postgreslXY-plpython/{Makefile,pkg-descr} to
postgresl95-plpython/{Makefile,pkg-descr}
Adjust all other postgresqlXY-plpython/Makefile to include the new master
Remove postgresql90-server
Reviewers: jgh, girgen, #portmgr, O5 Ports Framework, bapt, crees
Reviewed By: #portmgr, O5 Ports Framework, bapt, crees
Subscribers: mat
Differential Revision: https://reviews.freebsd.org/D6898
The last change submitted or approved by Horia in Bugzilla dates back to
September 2015. Since then, all commits to his ports were landed by others
after the maintainer timeout period expired (see r383744, r405055, r405057,
r400461 and r414655, for example).
Horia did show interest in coming back after I sent a private email a few
months ago, but since nothing has changed it is better to reassign his ports
back to the heap.
Differential Revision: https://reviews.freebsd.org/D5980
- Added cast improvements to CegoFieldValue::castTo method, which are
also checked now with check050
- Evaluation of locale to find out decimal point character. E.g.
for english locales this is ., for german this is ,. The character
is used for float value handling in CegoFieldValue methods.
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
Tile38 is an open source (MIT licensed), in-memory geolocation data store,
spatial index, and realtime geofence. It supports a variety of object types
including lat/lon points, bounding boxes, XYZ tiles, Geohashes, and GeoJSON.
Features:
Spatial index with search methods such as NEARBY, WITHIN, and INTERSECTS.
Realtime geofencing through persistent sockets or webhooks.
Object types of lat/lon, bbox, Geohash, GeoJSON, QuadKey, and XYZ tile.
Support for lots of Clients Libraries written in many different langauges.
Variety of client protocols, including http (curl), websockets, telnet,
and the Redis RESP.
Server responses are RESP or JSON.
Full command line interface.
Leader / follower replication.
In-memory database that persists on disk.
WWW: http://tile38.com/
PR: 210147
Submitted by: olevole@olevole.ru
This only affects "Created by" lines with one exception: devel/uclcmd. There the maintainer is changed. This was overlooked in r416918.
Approved by: junovitch (mentor)
- 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>
p5-Term-ReadLine-(Gnu,Perl,TTYtter).
I can't find any reason for p5-ReadLine-Gnu to have been added as
ReadLine-Gnu instead of Term-ReadLine-Gnu twenty years ago.
devel/p5-Term-ReadLine-Perl was added as a dupplicate a few years back
where it should not have, so change its maintainer to be perl@ like
devel/p5-ReadLine-Perl had.
Sponsored by: Absolight
