Message-ID: <e50d1bc392eb97bdd161603b3a2c802c27a82c2c.camel@cybertec.at>
Subject: Re: Is CREATE INDEX dependent on the session?
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Ilya Priven <ilya.konstantinov@gmail.com>,
	pgsql-docs@lists.postgresql.org
Date: Thu, 28 Sep 2023 08:23:35 +0200
In-Reply-To: 
 <CA+dzQZ11kt9X3bBoig+CtCtNp_z6sqqXMe4WxArHi97+gYCxqg@mail.gmail.com>
References: 
	<CA+dzQZ11kt9X3bBoig+CtCtNp_z6sqqXMe4WxArHi97+gYCxqg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/e50d1bc392eb97bdd161603b3a2c802c27a82c2c.camel%40cybertec.at>
Precedence: bulk

On Wed, 2023-09-27 at 11:23 -0400, Ilya Priven wrote:
> Would it warrant a clarification in the documentation:
> - Whether CREATE INDEX is aborted if the session is disconnected, assumin=
g it's not in a transaction?

It is aborted as soon as the server realizes that the client is gone, which=
 may
take a while (see the keepalive parameters and "client_connection_check_int=
erval").

> - Ditto for CREATE INDEX CONCURRENTLY?

The answer is the same.
Note that if CREATE INDEX CONCURRENTLY is interrupted, you are left with an
INVALID index that you have to delete later.

> - Whether CREATE INDEX CONCURRENTLY "returns" immediately or blocks the s=
ession until it's created?

It blocks until the index has been created.

Do you want to propose a patch?

Yours,
Laurenz Albe