MySQL Consulting - MySQL Support - MySQL Remote DBA - PostgreSQL Consulting - PostgreSQL Support - PostgreSQL Remote DBA

How to implement “as of” queries in PostgreSQL?

In PostgreSQL, you can implement “as of” queries using the SQL standard’s temporal query features, which allow you to query a table as it existed at a specific point in time. There are two main […]

How to compute cost of slow query in PostgreSQL?

The cost of a slow query in PostgreSQL can be estimated by the Query Planner, which uses statistics about the data in the tables being queried to make predictions about the query execution time. The […]

How are Global Indexes implemented in PostgreSQL?

In PostgreSQL, global indexes are implemented using a shared-nothing architecture, which means that the index data is partitioned and distributed across multiple physical nodes or “shards.” This allows for parallel query processing and improved performance […]

How to implement PostgreSQL synchronous_commit options and Synchronous Standby Replication?

PostgreSQL provides the option of synchronous replication to ensure that transactions are committed on the standby servers before they are acknowledged as being committed on the primary server. This can provide an added level of […]

When is hard parsing optimization taking more time in PostgreSQL?

In PostgreSQL, hard parsing optimization typically takes more time when a query is submitted for the first time or when the database statistics or query planner configuration has changed significantly. This is because hard parsing […]

Tuning Process Global Area in PostgreSQL

In PostgreSQL, the process global area (PGA) is managed by the server’s memory allocator and is used to store data structures associated with each client’s session, such as query plans and sorts. To tune the […]

Can I turn off redo log generation in PostgreSQL?

No, it is not possible to turn off redo log generation in PostgreSQL, as it is a fundamental part of the transactional system that ensures the durability and consistency of your data. The redo logs […]

What does a COMMIT do internally to PostgreSQL?

In PostgreSQL, a COMMIT statement is used to finalize a transaction and make its changes permanent in the database. When a COMMIT statement is executed, the following things happen internally in PostgreSQL: After a transaction […]

How Latches are implemented in PostgreSQL?

PostgreSQL uses latches to provide synchronization between different threads accessing shared resources. Latches are lightweight and efficient mechanisms that provide mutual exclusion between threads. Here is a table describing all the PostgreSQL latches, their purpose, […]

Configuring PostgreSQL for optimal usage of available RAM

PostgreSQL has several configuration parameters that control its memory usage. Here is a detailed description of some of the most important memory-related parameters: It is important to monitor the memory usage of the database process […]

* Everything changes over time – Our blogs/posts and comments changes over time, That’s how it should be! Whatever we comment from MinervaDB Inc. Teams (including Shiv Iyer) and other stakeholders or guest bloggers posted here are never permanent, These things worked for us. But, there is no guarantee they will work for you too, When using the recommendations from ChistaDATA or MinervaDB or MinervaSQL or any other online resources / Google, You must test the advice before applying them to your production systems, and always invest for a robust Database DR solution, Thank you for understanding.

Discounts are applicable only for multi-year contracts / long-term engagements, We don’t hire low-quality and cheap rookie consultants to manage your mission-critical Database Systems Infrastructure Operations and so our consulting rates are competitive. Being a virtual corporation (no physical offices anywhere in the world), whatever you pay go directly to our consultant’s fee. It’s impossible for us to offer you low-cost consulting, support and remote DBA services with elite-class team, Thanks for understanding and doing business with MinervaDB.

PostgreSQL is a registered trademark of the PostgreSQL Community Association. ClickHouse is a registered trademark of ClickHouse, Inc. MongoDB is a registered trademark of MongoDB, Inc. Couchbase is a registered trademark of Couchbase, Inc. Redis is a registered trademark of Redis Ltd. Apache Cassandra is a registered trademark of the Apache Software Foundation. Milvus is a registered trademark of Zilliz. MinIO is a registered trademark of MinIO, Inc. Amazon Redshift and Amazon Aurora are registered trademarks of Amazon.com, Inc. Google Cloud is a registered trademark of Google LLC. Snowflake is a registered trademark of Snowflake Inc. Databricks is a registered trademark of Databricks, Inc. MySQL and InnoDB are registered trademarks of Oracle Corporation. Oracle is a registered trademark of Oracle Corporation. MariaDB is a trademark of MariaDB Corporation Ab. All other trademarks are property of their respective owners. Other product or company names mentioned may be trademarks or trade names of their respective owner. Copyrights © 2010-2025. All Rights Reserved by MinervaDB®.

The Data Transformation Company

Data Architecture, Engineering and Operations for SQL, NoSQL, NewSQL, Cloud Native Data Platforms, Analytics and AI

PostgreSQL Performance