Bobcares

PostgreSQL CREATE INDEX CONCURRENTLY – About

by | Jul 23, 2023

Learn more about CREATE INDEX CONCURRENTLY in PostgreSQL. Our PostgreSQL Support team is here to help you with your questions and concerns.

PostgreSQL CREATE INDEX CONCURRENTLY – About

The CREATE INDEX CONCURRENTLY statement in PostgreSQL lets us create an index on a table without blocking write operations on the table.

In other words, other transactions can continue to insert, update, or delete data while the index is being created. However, the CREATE INDEX CONCURRENTLY operation may sometimes encounter a “waiting” state.

PostgreSQL CREATE INDEX CONCURRENTLY - About

When we run a CREATE INDEX CONCURRENTLY statement, PostgreSQL acquires a ShareUpdateExclusiveLock on the table. This lock lets the index creation process read the table’s existing data while allowing other write operations to proceed.

In case there are other transactions that hold incompatible locks, like an exclusive lock or AccessExclusiveLock, on the table, the CREATE INDEX CONCURRENTLY operation will enter a “waiting” state. In other words, the operation waits until the conflicting locks are released before proceeding with the index creation.

The duration of the waiting state varies according to the lock conflicts and the activity on the table. If there are no or minimal conflicting locks it will be a short wait. However, if there are active transactions holding exclusive locks on the table, it will be a longer wait.

Our experts would like to point out that the waiting state during concurrent index creation is a normal part of the process and does not indicate an error or problem with the database. In fact, it helps balance the need for creating the index and maintaining write concurrency.

Additionally, we can query the pg_stat_progress_create_index system view to monitor the progress of the concurrent index creation. This helps us check if it is still waiting or actively building the index.

In fact, it offers us information about the progress of index creation, including the current state, percentage completion, etc.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Techs introduced how to use the CREATE INDEX CONCURRENTLY statement in PostgreSQL

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF