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

How Materialised Views work in PostgreSQL?

Materialized views in PostgreSQL are useful when you have frequently used queries that are complex, slow, or involve large amounts of data. In such cases, creating a materialized view can significantly improve query performance. A […]

How to prevent Replication Break in MySQL while adding INDEX/COLUMN using PT-OSC (pt-online-schema-change)?

When adding indexes or columns in MySQL, it is important to be aware of the potential for replication to break. One way to prevent this is to use a tool like pt-online-schema-change from the Percona […]

How MySQL 8 reduced contention for metadata locks?

MySQL 8 introduced several improvements to reduce contention for metadata locks, which are locks that are used to manage access to database objects such as tables and indexes. Here are a few ways in which […]

How invisible indexes in MySQL 8 works?

In MySQL 8, invisible indexes are a feature that allows you to create an index without it being used by the optimizer. This can be useful in situations where you want to test the impact […]

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 […]

What happens to uncommitted transactions in MySQL if the server crashes after the update?

In MySQL, if the server crashes after an update and the transaction was not committed, the changes made by the transaction will be rolled back during the crash recovery process. This is because MySQL uses […]

Why SELECT * from is bad for SQL performance?

Using SELECT * can be bad for SQL performance for several reasons, including the following: Overall, it is best practice to only select the columns that are needed for a query, rather than using SELECT […]

* 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

MinervaDB