Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pB0Ts-0003yR-N3 for pgsql-bugs@arkaria.postgresql.org; Thu, 29 Dec 2022 21:30:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pB0Tq-00077U-QP for pgsql-bugs@arkaria.postgresql.org; Thu, 29 Dec 2022 21:30:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pB0Tq-00077J-Gy for pgsql-bugs@lists.postgresql.org; Thu, 29 Dec 2022 21:30:26 +0000 Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pB0Tj-0006cN-H7 for pgsql-bugs@lists.postgresql.org; Thu, 29 Dec 2022 21:30:25 +0000 Received: by mail-pj1-x1033.google.com with SMTP id o1-20020a17090a678100b00219cf69e5f0so24084698pjj.2 for ; Thu, 29 Dec 2022 13:30:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yugabyte.com; s=google; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=U7rKkTTtAIg1VdKeuOTk/6hE81ZjtXYzz5gDqiDNKqc=; b=KKfaYj1ftlT2jRFiWU0LJTouvTtyxkwVs0UXvXrFZ8FUMFbaBB5MumMGDdhVEgSFaw Ef3rvbq295xwIAs6jBs27pF9x7TXsN6kzdf+bmUmF1gxZ/ENEnmJTrnzlKyyM6mv2lCN YCKchaZqHTz5ZlOgFo9CR+oj3eBJ9cK74z4CM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=U7rKkTTtAIg1VdKeuOTk/6hE81ZjtXYzz5gDqiDNKqc=; b=mQBv3XQNP53I7XTVTU46evPnzHhOWnVsWV4Q9PIfEnJSYmzHZxPo+tB8MXAn7LuD3Y 97caP0x9t+IFlJQf/Nu8QoKUkBjAYouWdfo+jC4U0tQRw5UJGRDk+nR1uD/Q/dzS3mAj qroz4Ic00P8M8J+bLBa8KhSgo/iC19wz714HX68cOUhZM4mpB88HhR9MfGxDbUhmxCWH CLHWyEzxrL0svN/cPhmrYB3wgTePwcW0qDeIIkCMXLp048iZ2te8dnKlka7C4/7aolDo iwR18D530ba4v2Y1JUWbCuVhOCfFnLDkcf3cyqSDodcMSvyijKWwW93fP+HVf47Ruhnl jLAw== X-Gm-Message-State: AFqh2kocbWRRmKT6wZNPVgOHQqahf9tuQph+WZPVWfPaqdU+glU2UTSS 4Ikbsa4Mk3DQd16gae9gSuqKAQ== X-Google-Smtp-Source: AMrXdXuZSvRlywSV9giwgPVDT8EqY0M2BqC1x+NaAKXV/oF+3JONrL5hgZXPQ0311bdYpKdOWMK50w== X-Received: by 2002:a05:6a20:bb10:b0:ad:2c7c:9510 with SMTP id fc16-20020a056a20bb1000b000ad2c7c9510mr32898038pzb.19.1672349417897; Thu, 29 Dec 2022 13:30:17 -0800 (PST) Received: from smtpclient.apple ([2601:646:101:7fda:7d66:1660:3469:79dd]) by smtp.gmail.com with ESMTPSA id e32-20020a630f20000000b00478fd9bb6c7sm11388533pgl.75.2022.12.29.13.30.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Dec 2022 13:30:17 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: BUG #17734: Doc bug: "initial database user" used where "bootstrap superuser" is meant From: Bryn Llewellyn In-Reply-To: Date: Thu, 29 Dec 2022 13:30:16 -0800 Cc: "pgsql-bugs@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <3C881305-83EA-4FD5-91DA-283EB2230DD7@yugabyte.com> References: <17734-53e1a947e5c663e2@postgresql.org> To: "David G. Johnston" X-Mailer: Apple Mail (2.3654.120.0.1.13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > david.g.johnston@gmail.com wrote: >=20 >> PG Bug reporting form wrote: >>=20 >> The following bug has been logged on the website: >>=20 >> Bug reference: 17734 >> Logged by: Bryn Llewellyn >> Email address: bryn@yugabyte.com >> PostgreSQL version: 15.0 >> Operating system: macOS Big Sur Version 11.7. >> Description: =20 >>=20 >> See =C2=AB37.1. The Schema=C2=BB >> (https://www.postgresql.org/docs/current/infoschema-schema.html): >>=20 >> =C2=AB >> This schema automatically exists in all databases. The owner of this = schema is the initial database user in the cluster, and that user = naturally has all the privileges on this schema... >> =C2=BB >>=20 >> See this "pgsql-general" thread: >> = https://www.postgresql.org/message-id/8A2C8B1B-470B-42F9-9694-C1EDDAC06266= @yugabyte.com. >>=20 >> It concluded with the decision the the proper term for the role that = the thread discusses is "bootstrap superuser". The proper term should = therefore be used consistently throughout the PG docs. >=20 > Yeah, we=E2=80=99ve come to an agreement on terminology but there is = work to be done to fix up the documentation to match. I=E2=80=99ve got = a thread out here somewhere with a first pass at it. I=E2=80=99ve = flagged this report to incorporate into the second pass. Whether that = patch is ultimately deemed a back-patchable bug fix hasn=E2=80=99t been = discussed though I=E2=80=99m mostly figuring it will be a v16 = improvement only. I=E2=80=99m not pushing to get something out before = the next minor release in any case. Thanks. No rush, of course.