Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqvMA-00E4eX-AU for pgsql-general@arkaria.postgresql.org; Wed, 18 Sep 2024 14:08:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sqvMA-00AR9u-1X for pgsql-general@arkaria.postgresql.org; Wed, 18 Sep 2024 14:08:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqg8K-00GfEw-58 for pgsql-general@lists.postgresql.org; Tue, 17 Sep 2024 21:53:16 +0000 Received: from mail-qk1-x732.google.com ([2607:f8b0:4864:20::732]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sqg8H-001hbI-Fz for pgsql-general@lists.postgresql.org; Tue, 17 Sep 2024 21:53:14 +0000 Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-7a9c3a4e809so439801685a.2 for ; Tue, 17 Sep 2024 14:53:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726609992; x=1727214792; darn=lists.postgresql.org; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=+5moUBR6i2Tgy2Liz6HYkwuwcVgWdYkXmMqqFg4qN0o=; b=ik5lQpz3oPI927U/1QqmIy1xvFalLU6O8QMstQpSmu/PZ1Q5YlnszPkUhN7Kb9bXmZ Qk061KtVECC+7SIhdNnyhFMAuqfSxULLIQAeeWGETF3xJU220ClT4ch4DIQRMzF7KmtV fSH7yQVZNimRoBdmtva9636MzXiVHyttReifO4wj3WQYBpofWeEHQYOiCQPDCRwAC5nF V/+b/Ph4O8cMWt5Z4aueN36mdqpHdJUvthAhkMbEPmvX07YdE7qqREyFfnkusBAhPvR6 mE1BBuAL19ItRK+h6Y6dNjG4waoxHmL7u40i/S5Mu25zbPsYPB56GetJyTxQHXTdOKI0 7O6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726609992; x=1727214792; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=+5moUBR6i2Tgy2Liz6HYkwuwcVgWdYkXmMqqFg4qN0o=; b=Z2S8jaKkHF8sJ9pjLvw0V2qpvsUvQy4HB2eCL1ey7thvELk1AgqG/1LsGwdlHKU0WQ L5vWUjBVIyvyGVV2DzXa2rreTfV72TpebuCj0DOy+dCMl1X5MNoeKujL2tSR3dZhIZPt RXlSG3Rm8hKD3hCIrBlwb1muVTXHUIUfUBd1dMIRnBok0xlyCmW5vmcb7Rrqu2abr8VC MHc6DWVZVzoW+SNx12DakChPOw+/RgUd+C6bEoO659luyMc0/zjjlG23A6ykTm0o1Dvr LA3w9nktAV82dIw4Ebf88iVlWrOZkMEu0Rwg09Q1OVlcjA6XTER8Ot2MBfo3WjnQMQiT m8Dw== X-Gm-Message-State: AOJu0YyZh7D18u2DAhGUtoWA8YDgB3Fcqfx1Vbcf4Wh+IPQkffFpJ8vH DMoNc82W61NhKI11yLv79RJaz2gomTD6+9GfNyt0rWVxvBC1USIIA2NU0w== X-Google-Smtp-Source: AGHT+IFVP0RqZFfjiIfFEiDVAzamB368dJGUsfzh63XfLwzWQqsLfSJeVIYHqMwRdrX+zpDrg171lw== X-Received: by 2002:a05:620a:294a:b0:79f:504:dead with SMTP id af79cd13be357-7ab30d43926mr2791144285a.27.1726609989471; Tue, 17 Sep 2024 14:53:09 -0700 (PDT) Received: from smtpclient.apple (syn-074-132-056-143.res.spectrum.com. [74.132.56.143]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7ab3e9b6367sm402776685a.66.2024.09.17.14.53.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 17 Sep 2024 14:53:08 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Wizard Brony Mime-Version: 1.0 (1.0) Date: Tue, 17 Sep 2024 17:52:58 -0400 Subject: CREATE DATABASE command concurrency Message-Id: <1E5F4E2E-EC7C-40E6-905F-F5EF6565F99A@gmail.com> To: pgsql-general@lists.postgresql.org X-Mailer: iPhone Mail (21E236) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk What are the concurrency guarantees of the CREATE DATABASE command? For exam= ple, is the CREATE DATABASE command safe to be called concurrently such that= one command succeeds and the other reliably fails without corruption?