Re: Unable to dump database using pg_dump
От | Adam Dear |
---|---|
Тема | Re: Unable to dump database using pg_dump |
Дата | |
Msg-id | 48505491.4040708@usnx.net обсуждение исходный текст |
Ответ на | Re: Unable to dump database using pg_dump (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Unable to dump database using pg_dump
|
Список | pgsql-general |
I managed to get the server started again. It was failing because the permissions on the data folder were not right. Now, though, I'm back to where I started. There are two postgres users in the pg_shadow table. One of them has a password, the other doesn't, but they both have the same sysid. I tried to delete the one without the password, I couldn't get it deleted. I tried: Delete from pg_shadow where ctid = '(0,1)'; DELETE 0 and Delete from pg_shadow where passwd = ''; DELETE 0 Tom Lane wrote: > Adam Dear <adear@usnx.net> writes: >> I'm not seeing the madisoncounty user in there. > > Odder and odder. It might be worth trying "vacuum freeze pg_shadow". > >> Also, I tried starting >> the db using /etc/init.d/postgres start, and it fails. > > Fails how? In particular, what shows up in the postmaster log? > >> Is that the >> proper way to get the service going, or should I be doing something else? > > The usual way to manually start/stop daemons on Linux is > > sudo /sbin/service postgresql start > sudo /sbin/service postgresql stop > > (omitting sudo if you're already root). I'm not sure offhand if there's > any real difference between that and just calling the init.d script > directly, but I believe that's how you're Supposed To Do It. > > regards, tom lane > >
В списке pgsql-general по дате отправления: