| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bryan Murphy <bmurphy1976(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade from 9.0.7 to 9.1.3: duplicate key pg_authid_oid_index |
| Date: | 2012-06-01 13:52:59 |
| Message-ID: | 24060.1338558779@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Bryan Murphy <bmurphy1976(at)gmail(dot)com> writes:
> The old 9.0 cluster was created by ubuntu. In this cluster there was an
> ubuntu user with an oid of 10 and a postgres user with an oid of 16386.
> The new 9.1 cluster was created with a custom build of postgres 9.1. This
> did not have an ubuntu user, and it had a postgres user with an oid of 10.
OID 10 is the bootstrap superuser, which is created with the name of the
operating system user that ran initdb. So the above does not sound like
anything to do with custom vs stock builds, but with who did initdb.
It seems that pg_upgrade needs a check to make sure that the bootstrap
superuser is named the same in old and new clusters.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2012-06-01 14:52:59 | Re: PostgreSQL 9.0.4 crashing |
| Previous Message | Bryan Murphy | 2012-06-01 13:45:41 | Re: pg_upgrade from 9.0.7 to 9.1.3: duplicate key pg_authid_oid_index |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-01 13:59:23 | Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque |
| Previous Message | Simon Riggs | 2012-06-01 13:49:39 | Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque |