DBMS > Linter vs. PostGIS vs. Vertica

System Properties Comparison Linter vs. PostGIS vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

RDBMS for high security requirements

Spatial extension of PostgreSQL

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

Relational DBMS

Spatial DBMS

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS

Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	0.10
Rank	#350	Overall
	#153	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	11.40
Rank	#43	Overall
	#27	Relational DBMS

Website

linter.ru

postgis.net

www.vertica.com

Technical documentation

postgis.net/documentation

vertica.com/documentation

Developer

relex.ru

OpenText

previously Micro Focus and Hewlett Packard

Initial release

1990

2005

Current release

3.4.2, February 2024

12.0.3, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

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

C and C++

C++

Server operating systems

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Data scheme

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

Secondary indexes

yes

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

SQL

Support of SQL

yes

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

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

character-based, interactive, front-end utility

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

user defined functions

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

based on PostgreSQL

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

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

yes

based on PostgreSQL

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

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

OCI Object Storage Completes Technical Validation of Vertica in Eon Mode
16 October 2023, blogs.oracle.com

Vertica by OpenText and Anritsu Sign New Deal for Next-Gen Architecture and 5G Network Capabilities
17 May 2023, PR Newswire

Stonebraker Seeks to Invert the Computing Paradigm with DBOS
12 March 2024, Datanami

OpenText expands enterprise portfolio with AI and Micro Focus integrations
25 July 2023, VentureBeat

OpenText integrates Micro Focus tech through Cloud Editions 23.3
26 July 2023, Techzine Europe

provided by Google News

Share this page