Re: [HACKERS] "CANNOT EXTEND" -
От | Tim Perdue |
---|---|
Тема | Re: [HACKERS] "CANNOT EXTEND" - |
Дата | |
Msg-id | 004501be6f4b$f24dae00$0b8c5aa5@timnt.weather.net обсуждение исходный текст |
Список | pgsql-hackers |
I still cannot get pg_dump to work since I fixed the system yesterday. This is a real mess and I need to make sure I have a current backup. -I upgraded from 6.4 -> 6.4.2 and applied the 2GB patch -I did "initdb" from the postgres user account -I cannot get pg_dump to work: ------- [tim@db /]$ pg_dump db_domain > /fireball/pg_dumps/db_domain.dump pg_dump error in finding the template1 database ------- At this point, the postmaster dies and restarts. I think I'm getting to where I need some real help getting this thing to dump again. The database is up and running just fine - I just cannot dump. Any tips or advice is GREATLY needed and appreciated at this point. All I need is it to take a dump ;-) Tim tim@perdue.net -----Original Message----- From: Bruce Momjian <maillist@candle.pha.pa.us> To: tim@perdue.net <tim@perdue.net> Date: Monday, March 15, 1999 11:57 AM Subject: Re: [SQL] Re: [HACKERS] URGENT - >> >> >> >From 6.4 -> 6.4.2 >> >> The production database is working well, but pg_dump doesn't work. Now >> I'm worried that my database will corrupt again and I won't have it >> backed up. > >6.4 to 6.4.2 should work just fine, and the patch should not change >that. Are you saying the application of the patch caused the system to >be un-dumpable? Or perhaps was it the stopping of the postmaster. I >can work with you to get it dump-able if needed? > >-- > Bruce Momjian | http://www.op.net/~candle > maillist@candle.pha.pa.us | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 >
В списке pgsql-hackers по дате отправления: