DBMS > Hypertable vs. PostgreSQL vs. TimescaleDB

System Properties Comparison Hypertable vs. PostgreSQL vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

An open source BigTable implementation based on distributed file systems such as Hadoop

Widely used open source RDBMS

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Wide column store

Relational DBMS

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

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Relational DBMS

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

Score	667.25
Rank	#4	Overall
	#4	Relational DBMS

Score	3.59
Rank	#72	Overall
	#5	Time Series DBMS

Website

www.postgresql.org

www.timescale.com

Technical documentation

www.postgresql.org/docs

docs.timescale.com

Developer

Hypertable Inc.

PostgreSQL Global Development Group

www.postgresql.org/developer

Timescale

Initial release

2009

1989

1989: Postgres, 1996: PostgreSQL

2017

Current release

0.9.8.11, March 2016

16.4, August 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GNU version 3. Commercial license available

Open Source

BSD

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

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

Linux
OS X
Windows

an inofficial Windows port is available

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

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

standard with numerous extensions

yes

full PostgreSQL SQL syntax

APIs and other access methods

C++ API
Thrift

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

Supported programming languages

C++
Java
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

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

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor on file system level

Source-replica replication

other methods possible by using 3rd party extensions

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

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

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.