A C implementation of the stored procedure written in plpgsql that's bundled
with OpenNMS, this is the preferred version for use as is offers better
performance
MySQL replacement : Percona ServerPercona Server is a drop-in alternative
for MySQL with enhanced performance and enterprise-grade features.
MySQL replacement : Percona ServerPercona Server is a drop-in alternative
for MySQL with enhanced performance and enterprise-grade features.
MySAC (Simple Asynchronous Client) is a library that provides mechanisms for
making asynchronous requests to MySQL database. It uses the official MySQL
client library for authentication and network functions. Memory allocation
must be done in user code, so any memory manager can be used.
DWH_File is used in a similar manner to NDBM_File, DB_File etc. In fact it
depends on one of these. DWH_File expands the functionality to save not
only the hash that is tied but also all the data that this hash contains
references to - that is it'll save all you list of lists and list of hashes
and so forth. And what's more, it will save objects as well - if they'll
comply with some very simple rules which don't impose any limitations to
their functionality or structure except that they can't themselves be tied
to anyone else. See the "Models" section of the embedded documentation for
details.
This module is an interface for Namazu library. Namazu is an implement
of full text retrieval search system.
Percona Toolkit is a collection of advanced command-line tools used by Percona
support staff to perform a variety of MySQL and system tasks that are too
difficult or complex to perform manually, including:
Verify master and replica data consistency
Efficiently archive rows
Find duplicate indexes
Summarize MySQL servers
Analyze queries from logs and tcpdump
Collect vital system information when problems occur
pgAgent is a job scheduler for PostgreSQL which may be managed using pgAdmin.
The official ODBC driver for connecting to PostgreSQL Database; not a
part of the PostgreSQL Database distribution, though -- developed and
maintained separately.
postgresql-relay can be used to as a single point of origin for all
your databases. Instead of having to remember (or modify in case
of changes) all the names of your databases, on which machines and
on which ports they are running, you only need to remember one
machine and the name of the database. The postgresql-relay will
then forward the connection to the proper database on the proper
port of the proper server. No more changes in the hundreds of clients
and scripts!