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. -- Oliver Elphick [EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA ======================================== "But the day of the Lord will come as a thief in the night. The heavens shall pass away with a great noise, and the elements shall melt with fervent heat, and the earth and the works that are therein shall be burned up." II Peter 3:10 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
