On Mon, 20 Mar 2023, David G. Johnston wrote:
>On Monday, March 20, 2023, Dávid Suchan
>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 hav
On Monday, March 20, 2023, Dávid Suchan
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?
>
>
Any chance you can in-line/bottom-post like the rest of us?
Anyway, you
Kópia: Tom Lane ; Daniel Gustafsson ;
pgsql-gene...@postgresql.org
Predmet: Re: pg_upgrade Only the install user can be defined in the new cluster
On Monday, March 20, 2023, Dávid Suchan
mailto:david.suc...@student.tuke.sk>> wrote:
rolname
---
anon
api
heartbeat
postgres
only t
On Monday, March 20, 2023, Dávid Suchan
wrote:
> rolname
> ---
> anon
> api
> heartbeat
> postgres
>
> only the default users..
>
You have an incorrect concept of default here. Only postgres is installed
by community PostgresSQL and thus pg_upgrade is rightfully complaining.
David
rolname
---
anon
api
heartbeat
postgres
only the default users..
Od: Tom Lane
Odoslané: štvrtok 16. marca 2023 19:24
Komu: Dávid Suchan
Kópia: Daniel Gustafsson ; pgsql-gene...@postgresql.org
Predmet: Re: pg_upgrade Only the install user can be
> On 16 Mar 2023, at 15:56, Dávid Suchan 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 p
=?Windows-1252?Q?D=E1vid_Suchan?= 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
3 10:28
Komu: Dávid Suchan
Kópia: pgsql-gene...@postgresql.org
Predmet: Re: pg_upgrade Only the install user can be defined in the new cluster
> On 15 Mar 2023, at 16:39, Dávid Suchan wrote:
>
> It prints out:
> count
> ---
> 1
I have a feeling the cluster you tried to u
> On 15 Mar 2023, at 16:39, Dávid Suchan 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 cl
It prints out:
count
---
1
(1 row)
Od: Daniel Gustafsson
Odoslané: streda 15. marca 2023 13:27
Komu: Dávid Suchan
Kópia: pgsql-gene...@postgresql.org
Predmet: Re: pg_upgrade Only the install user can be defined in the new cluster
> On 15 Mar 2023,
Gustafsson
Predmet: Re: pg_upgrade Only the install user can be defined in the new cluster
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 proceed with pg_upgrade and I dont know
how can i connect to it now
> On 15 Mar 2023, at 14:48, Dávid Suchan 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 proceed with pg_upgrade and I dont know
> how can i connect to it now ...
Sure, create a new cluster in *same way* you will f
> On 15 Mar 2023, at 10:30, Dávid Suchan 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
Hello, Im trying to upgrage the db version to a newer one with the command:
'/usr/lib/postgresql/14/bin/pg_upgrade --old-bindir /usr/lib/postgresql/9.6/bin
--new-bindir /usr/lib/postgresql/14/bin --old-datadir /etc/postgresql/9.6/main
--new-datadir /var/lib/postgresql/14/data -U postgres' (logged
14 matches
Mail list logo
