Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
Subject: Re: CREATE DATABASE command concurrency
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <1E5F4E2E-EC7C-40E6-905F-F5EF6565F99A@gmail.com>
Date: Wed, 18 Sep 2024 07:21:06 -0700
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D36748A9-A7FA-48DF-B8D0-A14E5DE545EF@thebuild.com>
References: <1E5F4E2E-EC7C-40E6-905F-F5EF6565F99A@gmail.com>
To: Wizard Brony <wizardbrony@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/D36748A9-A7FA-48DF-B8D0-A14E5DE545EF%40thebuild.com>
Precedence: bulk


> On Sep 17, 2024, at 14:52, Wizard Brony <wizardbrony@gmail.com> wrote:
>=20
> What are the concurrency guarantees of the CREATE DATABASE command? =
For example, is the CREATE DATABASE command safe to be called =
concurrently such that one command succeeds and the other reliably fails =
without corruption?

The concern is that two different sessions issue a CREATE DATABASE =
command using the same name?  In that case, it can be relied upon that =
one will succeed (unless it fails for some other reason, like lacking =
permissions), and the other will receive an error that the database =
already exists.=