| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Johann Spies <jspies(at)maties(dot)sun(dot)ac(dot)za> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Postgresql 7.1 dying on Debian Woody |
| Date: | 2001-06-29 14:38:43 |
| Message-ID: | 7220.993825523@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Johann Spies <jspies(at)maties(dot)sun(dot)ac(dot)za> writes:
> I happened yesterday while I was running a script copying about 58000
> entries to a table and I can not get it going again. From
> /var/log/postgres.log:
> The Data Base System is starting up
> /usr/lib/postgresql/bin/postmaster: Startup proc 12953 exited with
> status 512 - abort
> /usr/lib/postgresql/bin/postmaster: Startup proc 13036 exited with
> status 512 - abort
Very strange. If the startup process detects a problem, it should write
some kind of error message to the log before aborting. Are you getting
a core dump file in the $PGDATA directory?
One thing I'd suggest immediately is to update to 7.1.2 and see if the
behavior changes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-06-29 17:21:58 | Re: [PATCHES] Re: High Memory Usage Patch -- Disregard my last message |
| Previous Message | Johann Spies | 2001-06-29 09:23:42 | Postgresql 7.1 dying on Debian Woody |