It may happen that we created an index and yet PostgreSQL doesn’t use it. What could be the reason and how to fix it? We identified 10 distinct scenarios. Read on to find out. Important Things Indexes may be tricky. We already covered how they work inanother article. Let’s quickly recap important pa..

Many things can improve database performance. One of the most obvious solutions is to use indexes. This blog post will examine them in detail to understand how they work in PostgreSQL and what makes them useful.

Executing transactions is not atomic and takes time. For example, a single UPDATE statement might modify multiple rows, and the database system needs time to update each row. During this update process, another transaction might start and attempt to read the modified rows. This raises the question: should the other transaction read the new values of the rows (even if not all rows are updated yet), the old values of the rows (even if some rows have been updated), or should it wait? What happens if the first transaction must be canceled later for any reason? How should this affect the other transaction? Read on to understand!