Sign in Agent Mode
Categories
Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Reviews from AWS customer

7 AWS reviews

External reviews

5 reviews
from

External reviews are not included in the AWS star rating for the product.


4-star reviews ( Show all reviews )

    Harshwardhan Gullapalli

Automated financial data workflows have reduced manual entry and support accurate auditing

  • April 17, 2026
  • Review provided by PeerSpot

What is our primary use case?

The primary use case for PostgreSQL on Ubuntu is storing and managing structured financial data extracted from scanned documents through our AI pipeline. When we processed an invoice or a trial balance through our OCR and LLM system, PostgreSQL on Ubuntu became the persistent layer where all that extracted data lived, including account codes, amounts, dates, and confidence scores from all the models. The FastAPI backend would query PostgreSQL to retrieve those records, and chartered accountants would use them in the system to validate and map those extracted line items. If someone needed to trace where a particular account entry came from, PostgreSQL had the complete audit trail and raw extracted data ready to query.

PostgreSQL on Ubuntu integrated seamlessly with the rest of our stack. We used it alongside n8n automation workflows running on Docker, and those n8n instances would write processed data directly into PostgreSQL tables. The database became their central hub where financial data flowed through multiple stages of the pipeline, from initial extraction through LLM classification, through trial balance mapping, all the way to final storage. We also leveraged PostgreSQL on Ubuntu’s JSONB columns quite extensively since our LLM outputs were semi-structured JSON. Being able to store those flexible JSON objects directly in the database without needing a separate document store was invaluable. It simplified our architecture and made querying and data retrieval much more straightforward when we needed to filter or aggregate results for reporting.

PostgreSQL on Ubuntu is deployed on-premises on Hostinger in our organization.

What is most valuable?

The standout features PostgreSQL on Ubuntu offers were three things. First, JSONB support was huge. Since our LLM pipeline generated semi-structured JSON outputs with extracted fields and confidence scores, being able to store and query that JSON directly in PostgreSQL on Ubuntu without needing a separate document store was a massive win. It simplified our entire architecture. Second was reliability and stability on Ubuntu. We ran PostgreSQL on Ubuntu on a Linux server in production and it was rock solid. We never had unexpected crashes or data integrity issues, even under heavy batch processing loads. The backup tooling with pg_dump also integrated seamlessly into our automated workflows, so we had confidence our data was always safe. Third, indexing and query performance was excellent. When the FastAPI backend needed to retrieve specific financial records or filter by account codes for our trial balance mapping system, queries stayed fast and consistent even as the dataset grew. That performance directly translated to a snappier experience for the chartered accountants using the system, which mattered significantly.

The impact of PostgreSQL on Ubuntu was tangible for our organization. On the reliability front, once we had PostgreSQL on Ubuntu as our structured data layer, we eliminated a lot of manual data validation work. Before that, extracted financial data had nowhere consistent to land, so it was error-prone. With PostgreSQL on Ubuntu in place, we had a clean, queryable store that made validation straightforward. On the metrics side, the full automation pipeline, which PostgreSQL on Ubuntu was central to, achieved a 70% reduction in manual data entry effort for our chartered accountant clients. Instead of manually re-entering invoice or trial balance data, the system extracted it, stored it cleanly in PostgreSQL on Ubuntu, and made it immediately available for review and mapping. That was a massive productivity gain. On cost, we also saw benefits from not needing separate document stores or complex caching layers. PostgreSQL on Ubuntu handled both structured data storage and semi-structured JSON in one place, which simplified our infrastructure and reduced operational overhead. The reliability also meant fewer debugging cycles and data recovery incidents, which translated to less engineering time spent on firefighting and more time on feature extraction.

The way I measured that 70% reduction in manual data entry was straightforward. We tracked the time chartered accountants spent manually entering financial data before and after our full automation pipeline went live. We examined a sample of their typical workflows, such as processing and trial balancing or a set of invoices, and compared how long it took them to do that work manually versus using our system end-to-end. The 70% figure came from that comparison. The system handled extraction, classification, and mapping automatically, so they only needed to do light validation rather than full manual data entry. It was not a rigorous academic study with control groups.

What needs improvement?

Several things come to mind for improvements in PostgreSQL on Ubuntu. First, the monitoring and observability experience on Ubuntu could be smoother. Setting up proper visibility into query performance, slow query logs, and connection pool statistics requires additional tools such as pg_stat_statements or external monitoring solutions. It would be helpful if PostgreSQL on Ubuntu shipped with slightly more user-friendly native dashboards built-in, especially for developers who are not dedicated database administrators. Second, native vector similarity search would be valuable. We were doing semantic document retrieval as part of our pipeline, so we ended up using Pinecone as a separate vector database alongside PostgreSQL on Ubuntu rather than keeping everything in one system. PostgreSQL on Ubuntu has some emerging vector capabilities, but if native vector similarity search were more mature and performant out of the box, it would allow consolidating the architecture and reducing operational complexity. Additionally, full-text search, while functional, required extra configuration for our financial document use case. Having more intuitive defaults for that would lower the barrier to entry for search-heavy applications.

For how long have I used the solution?

I used PostgreSQL on Ubuntu throughout my time at Radiant Services, approximately one and a half years of hands-on production experience.

What do I think about the stability of the solution?

PostgreSQL on Ubuntu is stable.

How are customer service and support?

The customer support for PostgreSQL on Ubuntu is quite responsive. When I needed help with my vector search, I contacted them, and they provided substantial assistance.

What other advice do I have?

On the integration side, PostgreSQL on Ubuntu played well with our broader tech stack. The async driver we used, asyncpg, integrated smoothly with FastAPI, so our backend could handle concurrent requests efficiently without blocking on database calls. That was important when we were processing multiple documents in parallel. On extensions, we did not lean heavily into custom PostgreSQL on Ubuntu extensions, but the fact that they are available and well-maintained is reassuring for future use cases. On security, the role-based access control and pg_hba.conf gave us fine-grained control over who could access what, which was critical when handling sensitive financial data for chartered accountants. We could lock down access per application user and audit everything. PostgreSQL on Ubuntu’s strong ACID compliance meant we could trust data consistency, which is non-negotiable when dealing with financial records where accuracy is essential.

I give PostgreSQL on Ubuntu a rating of 8 out of 10. I chose this rating because there are improvements needed, such as native vector similarity search and smoother monitoring and observability experience on Ubuntu, particularly for developers who are not dedicated database administrators.

My advice to others looking into using PostgreSQL on Ubuntu would focus on connection pooling documentation and tooling, which is quite good. If you are building an AI or LLM-based application that produces structured or semi-structured data, which is increasingly common, PostgreSQL on Ubuntu is a genuinely strong choice. It is production-grade, battle-tested, and it handled our financial document processing workloads extremely well. My advice would be to use JSONB columns early if your outputs are schema-flexible, set up connection pooling with pgBouncer from day one, and if you need semantic search, combine PostgreSQL on Ubuntu with a vector database such as Pinecone rather than trying to consolidate everything into one system.

Also, automate your backups with pg_dump as part of your CI/CD setup from the start. Overall, PostgreSQL on Ubuntu is very good, and I am genuinely impressed with how reliable and performant it was in our production environment. It scaled well for our use case. As our document volume grew over time, PostgreSQL on Ubuntu handled increased load without requiring major architectural changes. Proper indexing and query optimization kept performance consistent, and the fact that it runs efficiently on Ubuntu meant we could scale vertically by adjusting server resources without changing much in our application layer. For teams expecting data growth, which is almost inevitable in AI-driven document processing, PostgreSQL on Ubuntu is an excellent choice.


    David François

Creating a sovereign trust machine has secured agricultural provenance and now builds global buyer confidence

  • April 04, 2026
  • Review from a verified AWS customer

What is our primary use case?

My main use case for PostgreSQL on Ubuntu is as the backbone of an agricultural provenance system called France Farms, with the primary goal of creating a trust machine for smallholder farmers in the Caribbean. I use PostgreSQL on Ubuntu to store critical agricultural data such as soil metrics, harvest origin, and chemical records. To ensure the data is tamper-proof, I implement cryptographic hashing such as SHA-256. This allows me to anchor a digital fingerprint to every physical asset, providing an immutable audit trail that can be verified by international buyers. Ubuntu LTS provides the stable open-source environment required to run these high-integrity database operations reliably at the edge.

What is most valuable?

The best features that PostgreSQL on Ubuntu offers for my solution include data integrity via pgcrypto. PostgreSQL on Ubuntu is not just a bucket for data; with the pgcrypto extension, it becomes a security vault. The ability to run SHA-256 cryptographic functions directly within the database engine is critical. It allows me to seal agricultural records at the point of entry, ensuring that the provenance of the produce is immutable from farm to buyer.

The stability of Ubuntu LTS kernel ensures that the system stays stable for years without breaking changes. For an IT project or a bio-IT project in the Caribbean context where hardware resources can be limited, having a lean, high-performance OS that handles PostgreSQL on Ubuntu's resource demands efficiently is a major challenge. Additionally, JSONB allows for flexible farming data. Farming data can be messy; one day I am tracking soil pH, and the next day I am tracking rainfall or GPS coordinates. PostgreSQL on Ubuntu's JSONB support allows me to store semi-structured data from different types of farm sensors without having to constantly redesign the database schema. It gives the trust machine the flexibility of a NoSQL database with the ACID-compliant reliability of a traditional SQL system.

PostgreSQL on Ubuntu has positively impacted my organization by being the single most important factor in moving France Farms from a conceptual bio-IT project to a functional sovereign trust machine because it has credibility with international farmers and partners. Using enterprise standard stacks, I can prove to global buyers that my data integrity is not just a claim; it is backed by the same architecture used by the world's largest tech firms. This has significantly lowered the trust barrier for Caribbean produce. It also enhances resource efficiency; when operating in a developing economy, I have to do more with less, and the lean nature of Ubuntu allows me to run high-performance database operations on modest hardware at the edge, reducing my overhead while maintaining a high percentage uptime for provenance records. Scaling with confidence is also key; knowing that I can seamlessly migrate my local Ubuntu and PostgreSQL on Ubuntu environment to AWS or other cloud providers as I scale is a massive strategic advantage. This allows me to build sovereign solutions locally while remaining cloud-ready for global expansion.

What needs improvement?

To better serve my sovereign bio-IT projects such as France Farms, PostgreSQL on Ubuntu could be improved in three key areas. First, a native GUI for hashing security management would be beneficial; while the pgcrypto extension is powerful, having a native Ubuntu-optimized graphical interface for managing cryptographic keys and audit logs would lower the barrier for non-expert administrators in the field. I have been good at this because I was really focused on getting France Farms to work, and I used my flavor of AI to assist me.

Second, automated edge-to-cloud syncing would be a game-changer; a built-in lightweight tool for offline-first synchronization would be invaluable in regions such as the Caribbean, South America, or Africa, where internet connectivity can be intermittent. Having a native Ubuntu service that manages PostgreSQL on Ubuntu data syncing to AWS automatically when the connection is restored would improve the trust machine's reliability.

Third, streamlined ZFS integration for data snapshots would help ensure absolute data integrity. Integrating ZFS file system snapshots directly onto PostgreSQL on Ubuntu management tools on Ubuntu would allow for transparent, instant, tamper-proof backups, giving sovereign projects an extra layer of defense against accidental data loss or hardware failure.

For how long have I used the solution?

I have been using PostgreSQL on Ubuntu for over a decade.

What do I think about the stability of the solution?

PostgreSQL on Ubuntu is very stable; it is regarded as the industry gold standard for stability. In the sovereign bio-IT context of my project for France Farms, stability is a requirement. If my trust machine crashes, the provenance of the produce is broken. Running PostgreSQL on Ubuntu 24.0 ensures access to security patches and updates. It also guarantees asset compliance; after atomicity, consistency, isolation, and durability, it means that even if the power goes out during a transaction, PostgreSQL on Ubuntu ensures that the data is 100 percent saved or rolled back. The synergy with the Linux kernel is excellent, as PostgreSQL on Ubuntu is a native Linux application that handles memory management and process scheduling incredibly well on Ubuntu.

What do I think about the scalability of the solution?

PostgreSQL on Ubuntu is a good scaling weapon due to its vertical scalability. Ubuntu is efficient with hardware resources, allowing me to scale up by simply adding more RAM to my local server. PostgreSQL on Ubuntu is renowned for its ability to utilize every bit of hardware power that is given to it. Additionally, JSONB enhances data scalability; in agriculture, for example, data shape changes frequently. One month, I could be tracking citrus yields, and the next day, I am adding carbon sequestration metrics. PostgreSQL on Ubuntu's JSONB, as a binary JSON, allows me to store diverse data types in a single table while keeping it indexed and fast.

How are customer service and support?

I have not needed customer support for PostgreSQL on Ubuntu yet, but because I use Ubuntu LTS, I still have access to the Ubuntu Advantage knowledge base and the Ask Ubuntu community. If a security patch is needed for the OS, it is pushed automatically. PostgreSQL on Ubuntu also has some of the most detailed technical documentation in existence.

How was the initial setup?

I found the process of setting up PostgreSQL on Ubuntu, along with the pgcrypto extension, to be straightforward, but it required a subtle understanding of the Linux command line interface. Using APT to manage the installation and updates is seamless. The repository system makes it easy to get stable, tested versions of PostgreSQL on Ubuntu that I need for a production environment. The challenge, or the real learning curve, was in the permissions and configuration. Managing the pg_hba.conf file to secure remote access while ensuring the PostgreSQL on Ubuntu user has the right ownership of the data was a hurdle. Understanding how Ubuntu handles systemd services for PostgreSQL on Ubuntu was key. Once I understood how to use systemctl to manage the database lifecycle properly, the setup became very reliable. I also received some help from artificial intelligence, which was very helpful for me.

What was our ROI?

I have seen a return on investment from using PostgreSQL on Ubuntu with a reduction in infrastructure cost; Ubuntu LTS is relatively free, allowing me to avoid the high monthly managed service fees from proprietary database platforms. This enables me to funnel my limited capital directly into R&D and soil science. There is also 100 percent data integrity with no licensing fees. Fewer employees are needed because this was bootstrapped for one person, so I did not need to hire a large team for a startup such as this.

What's my experience with pricing, setup cost, and licensing?

I chose to run PostgreSQL on Ubuntu directly onto Ubuntu LTS to maintain sovereign control over the pricing and setup cost.

Which other solutions did I evaluate?

Before choosing PostgreSQL on Ubuntu, I evaluated other options; specifically, I compared it with NoSQL, namely MongoDB, for its flexibility with unstructured agricultural sensor data, and SQLite for the edge nodes on the farms due to its zero configuration setup. While SQLite is great for small tasks, it lacks the enterprise security features and powerful pgcrypto extension required.

What other advice do I have?

The decision to use cryptographic hashing in my system was driven by a lack of transparency in traditional agricultural supply chains. In the Caribbean, smallholder farmers often struggle to prove the origin and quality of their produce to international buyers. The particular challenge was creating an immutable audit trail without requiring expensive, high-bandwidth blockchain infrastructure at the farm level. By using SHA-256 hashing within PostgreSQL on Ubuntu, I can generate a unique digital fingerprint for every harvest record at the point of entry. This ensures that if a middleman or a rogue actor tries to tamper with the data, such as changing the organic status or the harvest date, the hash will no longer match. It turns a standard database into a trust machine, giving local farmers the sovereign proof they need to compete in global markets.

The primary feature I wish existed for PostgreSQL on Ubuntu is a native provenance layer for blockchain-light anchoring. This would be an Ubuntu service that can automatically anchor PostgreSQL on Ubuntu hash stamps to a public or private ledger. AI-driven integrity audits are also necessary; a built-in Ubuntu tool that utilizes machine learning to scan PostgreSQL on Ubuntu records for anomalies or inconsistent patterns in my agricultural data would serve as an automated digital inspector for stakeholder farmers, catching errors or fraud before the produce leaves the farm. Additionally, a hardware-level root of trust, such as binding the database master key to a physical hardware chip on an edge device, would guarantee that the data remains sovereign and cannot be moved or decrypted if the hardware is stolen from a rural farm site.

The most important thing for me is the synergy between the Linux kernel and PostgreSQL on Ubuntu. In a bio-IT context, especially when dealing with physical assets such as soil and harvest, the database cannot be a black box. Because I am running PostgreSQL on Ubuntu, I have total visibility into how the system handles hardware via Udev, how it manages file systems, and how it secures the data at rest. This full-stack transparency is what makes a sovereign trust machine possible. It allows a developer in a developing country or a developing economy to build enterprise-grade security that can be verified globally. If someone wants to build for the edge, where trust is the primary currency, PostgreSQL on Ubuntu is the only choice.

My advice for anyone looking to deploy PostgreSQL on Ubuntu for high-integrity projects is to first master the command line interface; this means not relying on GUI wrappers. Understanding how to manage PostgreSQL on Ubuntu via the Ubuntu terminal and focusing specifically on systemd for service management and file permissions for data directories grants true sovereign control. Lean into the extensions; do not treat PostgreSQL on Ubuntu as a basic SQL bucket. Explore extensions such as pgcrypto for cryptographic hashing and JSONB for semi-structured data; these features will enable building complex trust machines without needing additional expensive middleware. Prioritize security at the edge; if building for the real world such as agricultural IT, focusing on the synergy between the Ubuntu kernel and the database is crucial. Understanding how the OS handles hardware triggers will help automate data entry and secure the root of trust at the physical layer. Lastly, build for the cloud, but stay sovereign; start development on a local Ubuntu LTS instance to learn the configuration deeply. Once the local environment has been mastered, migrating to AWS RDS becomes a seamless strategic move rather than a technical hurdle. I would rate my overall experience with PostgreSQL on Ubuntu at a nine out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)


    Rizwan Ghzzaal

Open-source database has given strong flexibility for operations and supports rapid cloud work

  • April 01, 2026
  • Review from a verified AWS customer

What is our primary use case?

I am working with PostgreSQL on Ubuntu as a consultant. I have been using PostgreSQL on Ubuntu from the open-source perspective. I have not used any license with PostgreSQL.

What is most valuable?

The biggest benefit in PostgreSQL on Ubuntu for me is the open-source advantage. Both the open-source aspect and the very strong community support provide significant value. I can do many multiple things rather than some very tightly-locked features from products that require license purchases and waiting for feature releases. From the out-of-the-box solutions, the community is very helpful and I can get solutions much faster.

Nowadays, with GenAI and AI tools available, there is a deposit of the entire knowledge base into one model. I get very fast support and help from GenAI as well. The biggest power for PostgreSQL on Ubuntu is the open-source aspect. Any open-source software allows me to look into the code, understand the logic, and mold my code according to it, and it will work perfectly rather than proprietary solutions where I am very much dependent on the vendor and have to wait for their next release to fix things.

What needs improvement?

PostgreSQL on Ubuntu could benefit from serverless support. Things have moved into the cloud, and it would be helpful to have an in-house serverless solution where we have distributed data. We could expand and reduce the servers behind the scenes with elasticity. I know this is a very complex thing because PostgreSQL on Ubuntu is atomic, and atomic databases have very consistent storage and all these things. However, it would be greatly helpful in planning capacity and in terms of if we need to expand in the future, we can expand, and in case it is not needed, we can shrink back. The elastic feature would be better if there were some solution like this.

Regarding scalability, PostgreSQL on Ubuntu is scalable, but if they have some native, more elasticity-induced capability, it would be beneficial. Currently, I am working on containers mostly, and containers are deployed and then destroyed. The database is always on very rigid servers which are hardly expanded or extended sometimes, but reduced, no. I cannot reduce them back because I do not know what sort of data I need and which sort of data I need to discard. That is a very difficult decision to make. If there is a feature regarding that, it would be nice to have. If there is not, it would be nice to have more native support for the cloud and this flexibility in data manipulation and data handling.

For how long have I used the solution?

I have been dealing with this solution for eight to nine years.

What do I think about the stability of the solution?

PostgreSQL on Ubuntu is stable. If something goes wrong, I would not blame PostgreSQL. I would only say that it is something that I need to fine tune. PostgreSQL on Ubuntu is handling my production infrastructures very well and it is going very good.

What do I think about the scalability of the solution?

Regarding scalability, PostgreSQL on Ubuntu is scalable, but if they have some native, more elasticity-induced capability, it would be beneficial. Currently, I am working on containers mostly, and containers are deployed and then destroyed. The database is always on very rigid servers which are hardly expanded or extended sometimes, but reduced, no. I cannot reduce them back because I do not know what sort of data I need and which sort of data I need to discard. That is a very difficult decision to make. If there is a feature regarding that, it would be nice to have. If there is not, it would be nice to have more native support for the cloud and this flexibility in data manipulation and data handling.

How was the initial setup?

The installation and deployment process of PostgreSQL on Ubuntu is very straightforward. I have automated it and I know that it is not about MySQL, but both of them have a very similar installation process. The main difference is the commands on how you manage MySQL and how you manage PostgreSQL on Ubuntu.

What was our ROI?

PostgreSQL on Ubuntu is open-source, and I have not spent a single penny other than the infrastructure on which it is hosted. If I look into the market, I have very heavy products, and even MySQL is also open source, but PostgreSQL on Ubuntu gives me a lot of savings in terms if I were to go to any other vendor which has a license. The ROI is significant because I am not paying a single penny for the product itself, but only for the underlying infrastructure.

What other advice do I have?

PostgreSQL on Ubuntu can be used for holding the data from the apps, helping with the logic, and retrieving the data, serving the data of clients, customers, and the user base. That is the main reason. PostgreSQL is a relational database. However, if there is something which is a non-relational database, a non-structured one, it goes to NoSQL options like MongoDB or DynamoDB in AWS.

The best advantage in PostgreSQL on Ubuntu is its flexibility for the users, for the developers actually. They are very much comfortable in designing the schemas. For me, it is very much flexible for maintaining the backups, the clusters, and running smooth operations. PostgreSQL on Ubuntu is very much flexible.

From the developer side, they are the ones that are using these features from PostgreSQL on Ubuntu. I am using it from the operational point of view: backup, security, and hosting it on a server or on the cloud. That is what my job is.

The performance for PostgreSQL on Ubuntu is very good and it is optimized. It gives me leverage of handling more queries at a time and speeds up the process.

There are features from the developer side regarding foreign data wrappers in integrating disparate data sources.

Since I am using PostgreSQL on Ubuntu in a very specific niche like maintenance, management, and backups, there is a very less chance I will find something negative about it because so far what I have used in the projects, I needed a thing and I needed a solution and it was there already. Everything was there already and it was smooth. However, more or less developers are the right person that can say this is a must-have feature that they miss in PostgreSQL on Ubuntu.

I have deployed a solution on AWS cloud with PostgreSQL on Ubuntu. I would rate this review as highly positive based on my extensive experience and satisfaction with PostgreSQL on Ubuntu.


    Debarshi Banerjee

Postgres has supported fast POCs and now serves both transactional data and AI vector workloads

  • March 30, 2026
  • Review from a verified AWS customer

What is our primary use case?

I am currently working with Prometheus for observability on top of a platform, making Prometheus my main tool. In my past project, I used Contentful as a headless CMS for content delivery.

I use standard Postgres and Prometheus in my current project, with no other tools of that sort for other use cases. The choice of database depends on the project, but mostly for any POC that I do, I choose Postgres because of its simplicity. In the AI world, it has pgvector, an index store that is good for RAG systems.

Basically, a transaction DB in our application as well as a vector store for our RAG pipeline is my central use case.

What is most valuable?

The good aspect about PostgreSQL on Ubuntu is the huge community support that we have. PostgreSQL on Ubuntu is open source software, and different teams have contributed to open source. So it is quite robust in providing a lot of things. If you think about on-the-fly aggregations, it also supports that. Distributed clusters are also supported. It is a tool that is right now very mature and able to handle a lot of use cases. Coming from a SQL background, PostgreSQL on Ubuntu is the standard tool that we use. Most of my use cases are sometimes POCs that I need to deliver. At that point, it is a no-brainer to just use PostgreSQL on Ubuntu because of its simplicity and familiarity.

What needs improvement?

The initial setup can be tricky. If you are going for some advanced things and have a lot of data, then you also have to think a lot about how to set up the cluster. The infrastructure of the cluster is something that you need to consider if you are hosting a lot of data. For a general use case, it is fine, but when it comes to scaling, you have to pay a little attention to the cluster. This is true for other search services as well, where you have to think about similar kinds of considerations. With Algolia, you did not have to worry because it was managed by the service layer itself. Since this is a more hands-on tool, once the data comes in and the volume is high, then you must also think about the infrastructure.

For how long have I used the solution?

I have more than five years of experience with PostgreSQL on Ubuntu. My usage has been on and off.

What do I think about the stability of the solution?

I have not seen any stability issues with PostgreSQL on Ubuntu in my day-to-day work. Maybe something we have done to our services has caused the issue, but we have not seen a core PostgreSQL on Ubuntu issue. PostgreSQL on Ubuntu is quite stable.

What do I think about the scalability of the solution?

If you are dealing with multiple regions and huge data with huge transactions per second, in that case, you have to set up the cluster. It is not impossible. You just need to know the right cluster settings to set it up.

Which solution did I use previously and why did I switch?

I have used Amazon OpenSearch services as a tool for similar purposes.

How was the initial setup?

PostgreSQL on Ubuntu is very easy in terms of installation and deployment.

What about the implementation team?

I have not done it personally. My team has done it. My DevOps team has provisioned AWS instances as well as Azure instances. Under the hood, I do not know what I am dealing with. For me, it is just an IP address that I can SSH into and do it. Where the cloud is running, I know for sure they are using AWS and Azure interchangeably.

What was our ROI?

ACID transactions basically talk about write queries. Basically, if it is a distributed system, it makes sure that transaction consistency is there on each of the transactions that is happening. Think about if you are in a different geographic location and your cluster is hosted in two different geographic locations, maybe one in South Pacific and one in Western Europe. In both cases, if write transactions are happening, this is a good way to basically order the transactions so that the eventual data consistency is there.

With the basic version, you can very quickly do POCs. That is a very good ROI for that because suppose you have to do a demo in one week and you want to just quickly bootstrap some services and get the solution up. It is a very good service to do that. However, with different use cases, maybe different solutions are better. If you are going for an e-commerce solution where you have multiple filters available and you have to show aggregation, then a different type of query and a different type of database is needed.

What's my experience with pricing, setup cost, and licensing?

I am not using the Algolia service. I have purchased something from AWS Marketplace.

Which other solutions did I evaluate?

I was just looking at a service called ClickHouse. ClickHouse also has a different type of database. It is a clickstream analysis database. What we are trying to do is instead of Prometheus, we are thinking of using ClickHouse in our project because of how fast it is. Under the hood, it does a different type of operations to do aggregations, sums, and other operations. Since it is a SQL-based query system, the familiarity is there.

What other advice do I have?

My overall rating for PostgreSQL on Ubuntu is nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)


    reviewer2805456

College projects have gained powerful data management for structured and JSON workloads

  • March 24, 2026
  • Review provided by PeerSpot

What is our primary use case?

My main use case for PostgreSQL on Ubuntu is for storing the database, and I'm using Ubuntu because it is open source. Like multiple operating systems, it will support it because one of my friends and teammates has a MacBook. So, we cannot use the normal one.

A specific example of how I use PostgreSQL on Ubuntu in my work is in my project titled a student management and faculty leave student rating management system and faculty leave management system. Here I am working on a project where students are applying, students can give ratings for the faculties, and faculties can apply for leave applications for the admin side or as their upper faculty. I am storing the SQL data, such as creating the tables and this kind of data in PostgreSQL. As I mentioned, my friend's laptop is a MacBook, so we are creating PostgreSQL on Ubuntu. During my internship, I used PostgreSQL to handle structured data and perform operations such as joining, indexing, and data retrieval. I find it very stable and efficient when working with a large database. Additionally, there is no limit for the operating system because it is supported in all operating systems, with maximum database being unlimited RAM and unlimited database size. The license is open source, so it is easy to use. Installation is straightforward, and I can access the database easily. We can also create our own user and database. We can easily manage the database, and we can use NoSQL data as well.

What is most valuable?

The best features PostgreSQL on Ubuntu offers in my experience are zero cost, because it is totally free and has no limits from any user. I can easily understand this kind of SQL. Additionally, the maximum database is free and open source, as I mentioned. It has strong performance with large datasets and huge databases, runs smoothly on Ubuntu, and remains stable across all operating systems. It supports advanced features such as JSON and XML, and provides better control.

These features make my work easier and more efficient because some databases do not support JSON. For example, SQL Server 2014 will only support XML datasets, not JSON. Nowadays, we are storing our data or extending our data with JSON files, so PostgreSQL is easy to use for these needs. Furthermore, PostgreSQL is better because it provides backup functionality such as the pg_dump utility, allowing us to easily take backups from the PostgreSQL on Ubuntu database. We can also add extensions and enhance features. Overall, PostgreSQL on Ubuntu is a powerful and reliable database management system; it is easy to use and good for students who want to move beyond basic and industry-level skills.

PostgreSQL on Ubuntu has positively impacted my organization in terms of saving my time within my college project. It is easy to learn and understand how it is used, with easy installation and ease of use as it is a free and open-source tool, which means there is no need to pay any money or deal with licensing costs.

What needs improvement?

PostgreSQL on Ubuntu can be improved by providing some inbuilt AI agent mode, as nowadays many applications are offering such features. The installation process can sometimes be confusing for new users, as it mostly relies on terminal commands where a small mistake can create issues. A more guided and simplified installation process would be helpful, along with improved documentation so users can easily install and use it. Additionally, we can enhance GUI support and modify the GUI design of the tool. Tools such as pgAdmin are available, but they are not always smoothly integrated, so a more seamless graphical interface could be beneficial. Clear error messages and troubleshooting support are also necessary.

For how long have I used the solution?

I have used PostgreSQL on Ubuntu in my college project but I do not know exactly how long I have been using it.

What do I think about the stability of the solution?

PostgreSQL on Ubuntu is stable in my experience because at one time there are more than one user using PostgreSQL on Ubuntu, and it properly provides answers to every user. It is scalable for the users.

What do I think about the scalability of the solution?

PostgreSQL on Ubuntu is completely scalable.

How are customer service and support?

Customer support for PostgreSQL on Ubuntu is good, and I find it satisfactory.

Which solution did I use previously and why did I switch?

Before using PostgreSQL on Ubuntu, I first used MySQL on Ubuntu for a different project. I switched because PostgreSQL was suited for different kinds of projects I was working on.

How was the initial setup?

I saved time due to the ease of installation, but I did not have the chance to compare it to other databases I have tried in detail.

What about the implementation team?

PostgreSQL on Ubuntu is deployed for my projects as I am using it as a user for my college project, but I do not know how my organization uses the PostgreSQL server on Ubuntu.

What was our ROI?

I have seen a return on investment because if someone purchases the functionality, they will find it investable due to the many features it provides and the overall better product. However, as I have not done any purchasing myself, I cannot say it is perfect; I can say it is better based on what I am aware of.

What's my experience with pricing, setup cost, and licensing?

My experience with pricing, setup cost, and licensing for PostgreSQL on Ubuntu is based on the fact that I am using it as a free source, free open source. Therefore, I have never needed to consider pricing or licensing.

Which other solutions did I evaluate?

I did not evaluate other options before choosing PostgreSQL on Ubuntu, as I was not looking into other alternatives.

What other advice do I have?

I would add that compared to other tools, PostgreSQL is perfect. It is open source and free, has strong performance, and good stability. It has advantages for JSON, XML, indexing, and is better for stored procedures and triggers while being good for real-world applications in large datasets and backend development.

My advice for others looking into using PostgreSQL on Ubuntu is that if you need to store structured and non-structured data while utilizing modern features, you can use PostgreSQL because it is perfect for storing databases, especially when handling JSON and XML files. It is simply the best. I would rate my overall experience with PostgreSQL on Ubuntu as an 8 out of 10.


    Francisco Javier Vergara

Reliable database has supported user growth and has delivered strong performance with low resource use

  • March 20, 2026
  • Review from a verified AWS customer

What is our primary use case?

PostgreSQL on Ubuntu is deployed as our application's database. Our application supports user registration, login, and other features that rely on a database. PostgreSQL stores artifacts, rules, strings, and all other data for our application. My setup and interaction with PostgreSQL on Ubuntu is standard with nothing unique to report.

What is most valuable?

PostgreSQL on Ubuntu offers reliability, performance, and cost-effectiveness, which were the primary factors in our decision to choose this database.

Regarding reliability and performance, I have not experienced any downtime, and the database has not shown any performance issues. The only challenge that arose was related to the growth of our own application; we had to tune our Postgres settings, but we could do this because of how flexible PostgreSQL on Ubuntu is. When configured correctly, PostgreSQL on Ubuntu demonstrates no performance issues.

PostgreSQL on Ubuntu has positively impacted our organization by providing software that seamlessly manages our database with our application. After reviewing alternatives, PostgreSQL on Ubuntu was the best fit for our needs.

Since implementing PostgreSQL on Ubuntu, I have noticed cost savings. While I cannot share metrics since we do not track them, we host our PostgreSQL within Docker images, and the resources used by those Docker images are consistently very low relative to all of the capabilities it provides.

What needs improvement?

PostgreSQL on Ubuntu can be improved in terms of flexibility, which comes at a cost—specifically its learning curve and complexity. This is not necessarily something that needs improvement, but it is something to consider when deciding which database to use. You need to invest significant time in learning PostgreSQL on Ubuntu. There is nothing related to documentation, support, or features I wish were easier to use.

For how long have I used the solution?

I have been using PostgreSQL on Ubuntu for almost eight years.

What do I think about the stability of the solution?

PostgreSQL on Ubuntu is stable.

What do I think about the scalability of the solution?

When configured correctly, PostgreSQL on Ubuntu is highly scalable.

How are customer service and support?

I have never used customer support for PostgreSQL on Ubuntu.

How would you rate customer service and support?

Which solution did I use previously and why did I switch?

I did not previously use a different solution.

How was the initial setup?

PostgreSQL on Ubuntu requires no license to use, and the setup cost is straightforward since we simply deploy a Docker image.

Which other solutions did I evaluate?

Before choosing PostgreSQL on Ubuntu, I did not evaluate other options.

What other advice do I have?

There is nothing related to extensions, security, or integration that I would like to mention.

My advice to others considering PostgreSQL on Ubuntu is to spend time learning how to tune the application to fit your performance and scalability needs; the earlier you do this, the easier it will be.

I would rate this product an 8 overall.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?


    Pranay Jain

Robust relational queries have supported secure user data growth and improve transaction safety

  • March 03, 2026
  • Review provided by PeerSpot

What is our primary use case?

The main use case for PostgreSQL on Ubuntu is storing the database and serving as our primary database for storing the credentials of users and other information, including candidate data and enterprise data. This covers my main use case.

What is most valuable?

The best features PostgreSQL on Ubuntu offers are complex joins, which allow us to perform advanced SQL queries, providing the atomicity of our tables, ACID properties for transaction safety, and scalability that we can expand to, as we currently have 10 lakh users, and it is easily scalable.

Complex joins are the best feature that PostgreSQL on Ubuntu provides because I have been using NoSQL solutions such as MongoDB, but PostgreSQL has better efficiency for complex queries when used correctly.

PostgreSQL on Ubuntu has positively impacted our organization because, from the initial phase with around 1,000 plus users during user accessibility testing, we defined the tables in such a manner that even with future scalability increases, it would function well, and now it has grown to 10 lakh users, still holding up well with fast data retrieval and good query performance, supported by effective indexing methods.

In our user table with PostgreSQL on Ubuntu, we initially added indexing on the email property, but after a while, we found that the phone number field was also frequently used, and adding indexing to it improved our query retrieving speed and efficiency by almost 20 to 30 percent.

What needs improvement?

From an improvement perspective, the UI of PostgreSQL on Ubuntu can be somewhat better because from my experience, it is outdated compared to current UI generations, and the reliability without changing the entire system architecture can also be improved, along with optimizing index management such as adding proper indexes and removing unused ones.

Documentation for PostgreSQL on Ubuntu can also be improved because it is quite old and not easy for most people to understand, so that is one area that could see enhancement.

For how long have I used the solution?

I have been using PostgreSQL on Ubuntu since 1.5 years.

What do I think about the stability of the solution?

From my experience, PostgreSQL on Ubuntu is very stable for our application.

What do I think about the scalability of the solution?

The scalability of PostgreSQL on Ubuntu is very good because complex joins are performed smoothly and efficiently; just ensure that the database structure is well-defined from the start to scale from 1,000 users to 10 lakh users or any number of future users.

How are customer service and support?

So far, we have not needed customer support for PostgreSQL on Ubuntu, but my initial inquiry about it was good.

Which solution did I use previously and why did I switch?

We used to use Microsoft SQL, but it was costing us too much as the size of the database grew, which is why we switched to PostgreSQL on Ubuntu, where its internal B-tree optimization is quite good, making it sufficient for our application.

How was the initial setup?

Regarding pricing and setup costs for PostgreSQL on Ubuntu, I do not have much information about pricing, but the initial setup was very easy, with the more tedious aspects appearing later during scaling; licensing is simple since it is open-source.

What was our ROI?

The return on investment with PostgreSQL on Ubuntu is very good compared to commercial databases such as Oracle or Microsoft SQL due to zero licensing cost and lower infrastructure costs, making it about 40 percent less expensive than licensed enterprise databases, and since there are no upfront licensing fees, the ROI is increased with a scalable system without exponential cost growth.

Which other solutions did I evaluate?

We evaluated Microsoft SQL and Oracle databases before choosing PostgreSQL on Ubuntu.

What other advice do I have?

I would rate PostgreSQL on Ubuntu a solid nine or ten because it is very good for our application.

I chose a nine out of ten because while it is very robust, scalable, and cost-effective for RDBMS databases, one drawback is that it can be a complex setup for beginners, needing tuning for very high-scale workloads, which can be tedious if the sizes of queries and databases increase.

For anyone looking to use PostgreSQL on Ubuntu, it is ideal for applications that have a clear vision of their database and table structures, and it provides faster query searches, proving to be quite efficient, and it can also be used alongside other NoSQL solutions.

A mid-sized firm, a smaller firm, or a larger firm that wants to create an application should choose PostgreSQL on Ubuntu as it is the best choice; it is reliable, scalable, and requires thoughtful consideration of database and table structures to leverage its capabilities fully.

You should ask about how query optimization can be done and indexing strategies that PostgreSQL on Ubuntu provides, as these are important aspects to consider when using any SQL kind of databases.

I rate this product a nine out of ten overall.


    Claudia Agosti

Advanced queries have powered feature engineering and ensured reliable data analysis

  • December 16, 2025
  • Review provided by PeerSpot

What is our primary use case?

My main use case for PostgreSQL on Ubuntu is to query the database and the tables.

A quick specific example of a task where I used PostgreSQL on Ubuntu to query the database or tables is that I query the tables with SQL code, and it is very smart. I do feature engineering directly in SQL.

What is most valuable?

The best features PostgreSQL on Ubuntu offers include advanced queries. Its extensions are very smart, such as PostGIS. It is very smart and flexible.

The advanced query feature has helped me because I can use CTE and window functions, subqueries, and complex subqueries, providing great flexibility.

PostgreSQL on Ubuntu has positively impacted my organization by being very reliable. It has solid recovery and the risk of data loss is very low. It is very robust and ideal for production projects.

What needs improvement?

PostgreSQL on Ubuntu can be improved because it is a bit slower than other solutions I have used. I would also appreciate the ability to use the EXPLAIN ANALYZE tool.

What do I think about the stability of the solution?

PostgreSQL on Ubuntu is stable.

What do I think about the scalability of the solution?

PostgreSQL on Ubuntu's scalability is good.

How are customer service and support?

I have not had any experience with customer support.

Which solution did I use previously and why did I switch?

Before PostgreSQL on Ubuntu, I previously used MySQL, but it is inferior in comparison.

What was our ROI?

I have seen a return on investment with PostgreSQL on Ubuntu through time saving.

Which other solutions did I evaluate?

Before choosing PostgreSQL on Ubuntu, I evaluated MySQL as another option.

What other advice do I have?

Since using PostgreSQL on Ubuntu, I have seen specific outcomes such as being very solid with no loss of data, which saves time.

My advice to others looking into using PostgreSQL on Ubuntu is to use it to improve coding and to improve skills in feature engineering and in coding with window functions or data ingestion with JSON or the integration with Python, R, and Jupyter Notebook. I have given this review a rating of 8.


showing 1 - 8