BUG #13916: Only the install user can be defined in the new cluster

Started by Reiner Peterkeabout 10 years ago2 messagesbugs
Jump to latest
#1Reiner Peterke
reiner.peterke@splendiddata.com

The following bug has been logged on the website:

Bug reference: 13916
Logged by: reiner peterke
Email address: reiner.peterke@splendiddata.com
PostgreSQL version: 9.5.0
Operating system: centos 7.0.1406
Description:

This appears buggy to me or at least inconsistent.

using pg_upgrade to upgrade from 9.4.5 to 9.5.0

the upgrade runs then at the end prints.
Only the install user can be defined in the new cluster.
Failure, exiting

But when i look in the 9.5 cluster everything appears to be working with all
users.

I don't understand the error message especially since it appears to have
succeeded in the upgrade.

Am i missing something?

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Michael Paquier
michael@paquier.xyz
In reply to: Reiner Peterke (#1)
Re: BUG #13916: Only the install user can be defined in the new cluster

On Thu, Feb 4, 2016 at 6:40 PM, <reiner.peterke@splendiddata.com> wrote:

This appears buggy to me or at least inconsistent.
using pg_upgrade to upgrade from 9.4.5 to 9.5.0
the upgrade runs then at the end prints.
Only the install user can be defined in the new cluster.
Failure, exiting

This error message comes from the following bit in pg_upgrade:
/*
* We only allow the install user in the new cluster because other defined
* users might match users defined in the old cluster and generate an
* error during pg_dump restore.
*/
if (cluster == &new_cluster && atooid(PQgetvalue(res, 0, 0)) != 1)
pg_fatal("Only the install user can be defined in the new cluster.\n");

This means that when running pg_upgrade there should not be users
created in the new cluster deployed except the user created for
installation. So, didn't you create extra users in your new cluster
before running pg_upgrade? I am not really seeing a bug here.
--
Michael

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs