Thread: pg_upgrade Only the install user can be defined in the new cluster

> On 15 Mar 2023, at 10:30, Dávid Suchan <david.suchan@student.tuke.sk> wrote:

> ..there are no other users in the db.

The check in question performs this:

    SELECT COUNT(*) FROM pg_catalog.pg_roles WHERE rolname !~ '^pg_';

What do you get when running that in the new v14 cluster?

--
Daniel Gustafsson

> On 15 Mar 2023, at 14:48, Dávid Suchan <david.suchan@student.tuke.sk> wrote:
>
> Can i create a brand new cluster and check it that way? Since I had to stop / shut down the 14 cluster in order to
proceedwith pg_upgrade and I dont know how can i connect to it now ... 

Sure, create a new cluster in *same way* you will for the upgrade and control
that.

--
Daniel Gustafsson

> On 15 Mar 2023, at 16:39, Dávid Suchan <david.suchan@student.tuke.sk> wrote:
>
> It prints out:
>  count
> -------
>      1

I have a feeling the cluster you tried to upgrade to doesn't match this one, as
the check that failed will fail on values other than 1.  Did you create them
equally?  If you try to upgrade into this cluster, even just with the --check
option, does that yield more success?

--
Daniel Gustafsson

=?Windows-1252?Q?D=E1vid_Suchan?= <david.suchan@student.tuke.sk> writes:
> The ' SELECT COUNT(*) FROM pg_catalog.pg_roles WHERE rolname !~ '^pg_'; ' prints count 4

4?  That would be the problem all right.  What are those, that is what
do you get from

SELECT rolname FROM pg_catalog.pg_roles WHERE rolname !~ '^pg_';

on the new cluster?

            regards, tom lane

> On 16 Mar 2023, at 15:56, Dávid Suchan <david.suchan@student.tuke.sk> wrote:
>
> So I tried upgrading into this brand new cluster I created(using initdb -D /somedatapathichose). Running the upgrade
with--check worked, it returned message that the clusters are identical. Then I stopped the new cluster, and ran the
pg_upgradewithout --check, which resulted in another: 
> Checking database user is the install user

pg_upgrade --check does not alter the new cluster in any way, so you must have
some form of processing on your system that configured the new cluster with
roles (and possibly other things) in between these runs.

--
Daniel Gustafsson

 rolname

-----------

 anon

 api

 heartbeat

 postgres

only the default users..

I installed both postgres versions on ubuntu machine with 'apt-get install postgres', which installed both client and server packages. Is that where I made a mistake?

On Mon, 20 Mar 2023, David G. Johnston wrote:

>On Monday, March 20, 2023, Dávid Suchan <david.suchan@student.tuke.sk>
>wrote:
>
>> I installed both postgres versions on ubuntu machine with 'apt-get install
>> postgres', which installed both client and server packages. Is that where I
>> made a mistake?

>Anyway, you had to have done more than that to use those other roles to
>appear in the new cluster.

And the Debian instructions are pretty clear, they tell one to
first drop the new version’s per-default-installed cluster then
upgrade the old cluster (into a fresh new one).

bye,
//mirabilos
--
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)