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 1l4VRW-0001xQ-HJ for pgsql-docs@arkaria.postgresql.org; Tue, 26 Jan 2021 21:00:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l4VRT-0000Od-Qn for pgsql-docs@arkaria.postgresql.org; Tue, 26 Jan 2021 21:00:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l4Rx9-0003pR-P0 for pgsql-docs@lists.postgresql.org; Tue, 26 Jan 2021 17:16:31 +0000 Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l4Rx2-0007So-Di for pgsql-docs@lists.postgresql.org; Tue, 26 Jan 2021 17:16:30 +0000 Received: by mail-qk1-x72a.google.com with SMTP id v126so16601380qkd.11 for ; Tue, 26 Jan 2021 09:16:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybercoment-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gUPit7SojtGY4Kp0GseglDmwBG8HJ0XW+9uRRRV+NQk=; b=V25Y8dVEQG0U11awK25lYdtHmueLMcrCMHrty4J4AF4FbUxWlx9q4kge3Q0ej2K4DN a5cxj2c060ipy07YnL9Umh1HpV2dClBMNb0S/nWx9RcaXiA997cB+P0JWW7vMTJxNOvx E2B2F9+uzRIoXtnYbPYZoICXQSMBhsq7AmeGnffpm9e5qNc3Way2dlqnlP6fgRYY0HlY EAiiKoW+P6rqSebFRMvTBWfT9wFdmv+ifZBlQobxrKr8U2k3xRZs0mzp9nz74lcSYqQG B95ka0FWKxzqmrWZRvwdQd5PNltTkHCU5F1H5g0oXTJljoDMDraJbJRtUmZwef9Lu1V+ x9xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gUPit7SojtGY4Kp0GseglDmwBG8HJ0XW+9uRRRV+NQk=; b=an/F36VVwMAyGScvdIDSneGF7VPYMJEX/wGmj9anccaPfOkjF2ZU9VTWTNRpIuEKkM Wlm0df0cw+1E/dWgGQbUHjLPN5YF+PtsjvREOyd39ridXgBWDPTrDIjYWPAA/9HyjINl /CUvSZv4nbnb2yYWnTfzcTUYwM3k/Wprj9lQdyNT/zJQyV4JIozv0bSVGhIQGK20DhhO 9cRhR1VcilX1As+M3eo55IerGteyzumjTqX1Fqmxwa15RpdFbKOh1dRVhHFWefVqJkeS byowaXGt7weIsrHRtwR15BsD4Pr8zoRwWfa7a3Hvqtz3AZb2YJ7K3hg4aEJSYrjQLaS/ LZkw== X-Gm-Message-State: AOAM533EKE5IBgKoXobv6eWu6Ityy7pCYHrzT88hStCHltc5CRcry0RC i7Z5fUnU9I6B6zOwmW8cpwVbrtDJl0DMjw== X-Google-Smtp-Source: ABdhPJwHKLkmIp8/WClnUuLTT75Fszrf5GeEpqUE3bcWkIvbue6zrTygOR/sIOgAgCnqKIT+7aoC3Q== X-Received: by 2002:a37:88b:: with SMTP id 133mr6477149qki.425.1611681382255; Tue, 26 Jan 2021 09:16:22 -0800 (PST) Received: from hank.localdomain (205-178-107-98.s3423.c3-0.stk-ubr1.chi-stk.il.cable.rcncustomer.com. [205.178.107.98]) by smtp.gmail.com with ESMTPSA id p18sm6486882qkj.130.2021.01.26.09.16.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Jan 2021 09:16:21 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Postgres upgrade does not mention requirement to have only 1 user From: Charlie Hayes In-Reply-To: Date: Tue, 26 Jan 2021 11:16:20 -0600 Cc: pgsql-docs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <2AA2F2BC-FD29-49ED-BCF1-937E4192E54F@cybercoment.com> References: <161164427375.4070.1378381620788426246@wrigleys.postgresql.org> To: Laurenz Albe X-Mailer: Apple Mail (2.3445.9.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk It may say =E2=80=9Cin the new cluster=E2=80=9D but it was not clear to = me if that was =E2=80=9Cin the new cluster (before the upgrade = starts)=E2=80=9D or =E2=80=9Cin the new cluster (after the upgrade = completes)=E2=80=9D In hind sight everything makes sense, but in the present it was very = confusing. -Charlie > On Jan 26, 2021, at 2:39 AM, Laurenz Albe = wrote: >=20 > On Tue, 2021-01-26 at 06:57 +0000, PG Doc comments form wrote: >> Page: https://www.postgresql.org/docs/13/pgupgrade.html >> Description: >>=20 >> During the pg_upgrade process, a check is run to make sure >> pg_catalog.pg_roles has only a single non pg_* user, typically this = is just >> 'postgres'. If this check fails, the error message is "Only the = install user >> can be defined in the new cluster."; This message implies the user = executing >> pg_upgrade must match the the rolsuper in pg_catalog.pg_roles. >>=20 >> There's no indication in the documentation that the user table must = be >> flushed of all but the one user, nor does it prescribe a method to = move >> forward. The error message is not helpful; I only figured it out by = finding >> and reading the postgres source code. >=20 > The error message says "in the new cluster". >=20 > The documentation says, "Initialize the new PostgreSQL cluster" and = that there > is no need to start the cluster. That is a pretty strong indication = that it > is not necessary to create any objects there. >=20 > But perhaps it would not harm to be more explicit and add something = like > that: >=20 > "Do not create and users, tablespaces or other objects on the new = cluster." >=20 > Yours, > Laurenz Albe >=20