DBMS > PostgreSQL vs. Sphinx vs. TDSQL for MySQL

System Properties Comparison PostgreSQL vs. Sphinx vs. TDSQL for MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Open source search engine for searching in data from different sources, e.g. relational databases

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Score	5.72
Rank	#56	Overall
	#5	Search engines

Score	1.12
Rank	#172	Overall
	#77	Relational DBMS

Website

www.postgresql.org

sphinxsearch.com

www.tencentcloud.com/products/dcdb

Technical documentation

www.postgresql.org/docs

sphinxsearch.com/docs

www.tencentcloud.com/document/product/1042

Developer

PostgreSQL Global Development Group

www.postgresql.org/developer

Sphinx Technologies Inc.

Tencent

Initial release

1989

1989: Postgres, 1996: PostgreSQL

2001

2013

Current release

16.4, August 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

BSD

Open Source

GPL version 2, commercial licence available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

C++

Server operating systems

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

hosted

Data scheme

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like query language (SphinxQL)

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Proprietary protocol

JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

partitioning by range, list and (since PostgreSQL 11) by hash

Sharding

Partitioning is done manually, search queries against distributed index is supported

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.