PostgreSQL vs. Vertica Analytics Database

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
PostgreSQL
Score 8.8 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.N/A
Vertica Analytics Database
Score 10.0 out of 10
N/A
The Vertica Analytics Platform supplies enterprise data warehouses with big data analytics capabilities and modernization. Vertica was acquired and supported by OpenText, then sold to Rocket Software in 2026.N/A
Pricing
PostgreSQLVertica Analytics Database
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
PostgreSQLVertica Analytics Database
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
PostgreSQLVertica Analytics Database
Considered Both Products
PostgreSQL
Chose PostgreSQL
My expirence with other solutions is very limited, but what I saw/heard is, that on Azure the managed MS SQL Server is said to be more flexible and you can use it in a serverless-ish fashion. But on the other hand, PostgresSQL is still strong regarding its efficiency. And in my …
Chose PostgreSQL
Being open source, PostgreSQL offers the highest performance among its peers. It has a strong support community where we can find solutions to most of the queries. It's suited for GIS (Geospatial) based applications, making it unique from its peers. There are fewer databases …
Chose PostgreSQL
We had to use PostgreSQL as that is the DB preferred by our SaaS Provider.
Chose PostgreSQL
PostgreSQL holds it own against both these options. Some of these DBs are in play for certain needs but the majority are PostgreSQL because of cost and operational performance.
Chose PostgreSQL
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Chose PostgreSQL
MySQL is an Oracle product which has in itself some known issues due to that (support, contract terms). Based on my knowledge, PostgreSQL support everything that MySQL support (syntax wise) and it adds more improvements and syntaxes that make the life of database engineers and …
Chose PostgreSQL
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
Chose PostgreSQL
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
Chose PostgreSQL
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
Chose PostgreSQL
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Chose PostgreSQL
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
Chose PostgreSQL
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Chose PostgreSQL
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
Chose PostgreSQL
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
Chose PostgreSQL
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
Chose PostgreSQL
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Chose PostgreSQL
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Chose PostgreSQL
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Chose PostgreSQL
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets.
We are Linux based solutions and …
Chose PostgreSQL
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale.
SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
Chose PostgreSQL
We selected PostgreSQL due to the number of employees who have used it in the past.
The data consistency guarantees.
The multiple transaction isolation levels support.
Chose PostgreSQL
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
Chose PostgreSQL
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
Chose PostgreSQL
I think Postgres stacks up great against all modern database solutions and has continued to be a trend leader in this space.
Vertica Analytics Database
Chose Vertica Analytics Database
Vertica performs well when the query has good stats and is tuned well. Options for GUI clients are ugly and outdated. IO optimized: it's a columnar store with no indexing structures to maintain like traditional databases. The indexing is achieved by storing the data sorted on …
Chose Vertica Analytics Database
We have been evaluating Greenplum comparing with Vertica.
Chose Vertica Analytics Database
SAP HANA, Oracle, MySQL, and PostgreSQL are too heavyweight for achieving real-time latency requirements. Google BigQuery is limited to Cloud that makes hard to integrate with a large ingestion pipeline that may have both Cloud-based and on-prem components. Hadoop is much more …
Chose Vertica Analytics Database
MySQL and MS SQL Server are both fantastic RDBMS products. MS SQL Server goes a bit further since it has the builtin analytical functions. But it only scales so far. Once the data goes beyond capacity, getting results out just does not happen anymore. IBM Netezza and …
Chose Vertica Analytics Database
Presto would be a good solution that would be less expensive and would also allow direct querying of all our data on Hadoop while maintaining good speed.
Chose Vertica Analytics Database
Vertica is great for small low complex queries and has great query performance over the other technologies that I have worked with.
Vertica fails to Hive wrt scalability and resource isolation, where Hive exploits hadoop's resource isolation.
Presto is almost comparable to …
Chose Vertica Analytics Database
Vertica is much easier to manage; is just software (i.e. vs. Netezza), easier to scale and extend, with a very powerful query execution engine and storage layer. While other solutions (e.g. Greenplum) are just postgres clones that were extended to run at scale but still keep …
Best Alternatives
PostgreSQLVertica Analytics Database
Small Businesses
InfluxDB
InfluxDB
Score 9.0 out of 10
Google BigQuery
Google BigQuery
Score 8.7 out of 10
Medium-sized Companies
SQLite
SQLite
Score 8.0 out of 10
Cloudera Enterprise Data Hub
Cloudera Enterprise Data Hub
Score 9.0 out of 10
Enterprises
SQLite
SQLite
Score 8.0 out of 10
Oracle Exadata
Oracle Exadata
Score 9.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
PostgreSQLVertica Analytics Database
Likelihood to Recommend
8.3
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
9.0
(0 ratings)
-
(0 ratings)
Usability
8.3
(0 ratings)
-
(0 ratings)
Availability
9.0
(0 ratings)
-
(0 ratings)
Performance
7.0
(0 ratings)
-
(0 ratings)
Support Rating
9.3
(0 ratings)
7.9
(0 ratings)
Implementation Rating
9.0
(0 ratings)
-
(0 ratings)
Product Scalability
8.0
(0 ratings)
-
(0 ratings)
User Testimonials
PostgreSQLVertica Analytics Database
Likelihood to Recommend
Based on my experience, PostgreSQL is exactly what I imagine when thinking of a relational database: it is fast for querying and intuitive (if the underlying relations have been well written) and its writes are also efficient. Of course you need to know that a relational database is what you need, for example I would not recommend it if you have a lot of unstructured data that have no way to create a relation from and if you need to run heavy aggregations over your data, as it is not where PostgreSQL would shine.
Read full review
As someone just starting out with data analytics and warehousing vertica is a great tool for a small scale business. It has amazing performance and can scale upto TBs of data. It works well for any organization which has about 100 - 500 DAUs of the system. The system doesn't require a lot of ops overhead. Scaling for PB data and 1000s of DAU is vertica's weak point. The system is just not designed for large scale usage and still has a long way to go to improve scalability. There are experiments to run Vertica query engine on top of HDFS which seem promising, however - if you have the the Hadoop ecosystem you are better off going the HDFS + Presto/Impala/SparkSQL route. But if you are in the Hadoop ecosystem, you probably are already investing a lot in ops.
Read full review
Pros
  • The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
  • The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
  • The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
  • The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
Read full review
  • Column-oriented storage organization, which increases performance of queries.
  • Compression, which reduces storage costs and I/O bandwidth. High compression is possible because columns of homogeneous datatypes are stored together and because updates to the main store are batched.
  • Shared nothing architecture, which reduces system contention for shared resources and allows gradual degradation of performance in the face of hardware failure.
  • Easy to use and maintain through automated data replication, server recovery, query optimization, and storage optimization.
  • Support for standard programming interfaces ODBC, JDBC, ADO.NET, and OLEDB.
  • Integration to Hadoop with the capability to perform analytics on ORC and Parquet files directly.
Read full review
Cons
  • The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
  • I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
  • Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
Read full review
  • One time, one of the nodes wasn't coming up because of some ambiguity with the local data. Vertica wasn't able to fix it by itself and we were trying to remove the node out of the database and we couldn't do it. It would be great if that could be addressed. Luckily when we rebooted the whole server, some of the dead transaction got flushed because of which vertica was able to recover and the node came up.
Read full review
Likelihood to Renew
As a needed software for day to day development activities
Read full review
No answers on this topic
Usability
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
Read full review
No answers on this topic
Reliability and Availability
PostgreSQL's availability is top notch. Apart from connection time-out for an idle user, the database is super reliable.
Read full review
No answers on this topic
Performance
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
Read full review
No answers on this topic
Support Rating
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
Read full review
HP/Micro Focus Vertica support is in par with other bigger vendors. In addition to this, there is enough best practices documentation available for some of the most common ways you will use Vertica that makes it easy to get Vertica up and running.
Read full review
Online Training
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
Read full review
No answers on this topic
Implementation Rating
The online documentation of the PostgreSQL product is elaborate and takes users step by step.
Read full review
No answers on this topic
Alternatives Considered
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Read full review
MySQL and MS SQL Server are both fantastic RDBMS products. MS SQL Server goes a bit further since it has the builtin analytical functions. But it only scales so far. Once the data goes beyond capacity, getting results out just does not happen anymore. IBM Netezza and Teradata were both appliances that required different expertise than we had in house. Vertica was able to do the same, and in some cases better, on commodity hardware (frankly in our case old servers that were slated for recycling!) and at a small scale. In other words, Vertica we could grow slowly over time. Infobright is a great log processing database but for the functions we were looking to serve it just didn't have some of the features Vertica had that we felt were show stoppers.
Read full review
Scalability
The DB is reliable, scalable, easy to use and resolves most DB needs
Read full review
No answers on this topic
Return on Investment
  • A robust and reliable platform reduces the risk of data loss and confusion.
  • Using an almost free product is economical. No license fees = minimal ownership cost.
  • Efficiency is high due to quickness and excellent resource management.
  • PostgreSQL helps us achieve our goals, and there are no time-consuming management tasks.
Read full review
  • Vertica increased our productivity in analyzing the data and validating simple proof of concepts with our data.
  • Results of analytical queries produced from Vertica are used by all departments as well as part of some of our products.
Read full review
ScreenShots