DBMS > OpenSearch vs. PostgreSQL vs. Vertica

System Properties Comparison OpenSearch vs. PostgreSQL vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Widely used open source RDBMS

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

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Search engine
Vector DBMS

Relational DBMS

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

Relational DBMS

Column oriented

Secondary database models

Vector DBMS

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Spatial DBMS
Time Series DBMS

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

Score	17.38
Rank	#32	Overall
	#4	Search engines
	#2	Vector DBMS

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Score	9.78
Rank	#42	Overall
	#26	Relational DBMS

Website

github.com/opensearch-project
opensearch.org

www.postgresql.org

www.vertica.com

Technical documentation

opensearch.org/docs/latest

www.postgresql.org/docs

vertica.com/documentation

Developer

The OpenSearch Software Foundation

PostgreSQL Global Development Group

www.postgresql.org/developer

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2021

1989

1989: Postgres, 1996: PostgreSQL

2005

Current release

2.19, February 2025

16.4, August 2024

12.0.3, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

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

Linux

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

All search fields are automatically indexed

yes

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

SQL-like query language

yes

standard with numerous extensions

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

Java API
RESTful HTTP/JSON API

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

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

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

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

by using the 'percolation' feature

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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.