On Wed, Aug 25, 2004 at 05:57:35PM +0100, Oliver Elphick wrote:
> On Wed, 2004-08-25 at 17:09, Alvaro Herrera wrote:
> > On Wed, Aug 25, 2004 at 04:25:02PM +0100, Oliver Elphick wrote:
>
> > > Maybe recreating pg_user in the database will help. It is a global
> > > table, so if you have other databases where pg_user exists, copy the row
> > > from pg_class in that database to pg_class in the corrupted database.
> >
> > No, pg_user is a view on pg_shadow ...
>
> Fingers! view ... table ... thingy
>
> What I meant is that, since it is global, recreating the item in
> pg_class as a copy of the entry in another database should possibly get
> rid of the pg_dump problem. If you create a new view, the result will
> presumably not be restorable.
But pg_user is not global ...
alvherre=# select relname, relisshared from pg_class where relname = 'pg_user';
relname | relisshared
---------+-------------
pg_user | f
(1 fila)
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"No deja de ser humillante para una persona de ingenio saber
que no hay tonto que no le pueda enseñar algo." (Jean B. Say)
