| From: | Darren Reed <darrenr+postgres(at)fastmail(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Shoaib Mir <shoaibmir(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: How to reindex when unable to open relation? |
| Date: | 2008-02-27 05:13:28 |
| Message-ID: | 47C4F178.1050102@fastmail.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tom Lane wrote:
> Darren Reed <darrenr+postgres(at)fastmail(dot)net> writes:
> > Hmmm, from the logfile, signal 11, so it core dumped...
> > Of course the default built binary is -O2...
> > (gdb) where
> > #0 0x082114b8 in RelationCacheInitializePhase2 ()
> > #1 0x0821fa67 in InitPostgres ()
> > #2 0x081a7d8b in PostgresMain ()
> > #3 0x08184882 in ServerLoop ()
> > #4 0x0818545c in PostmasterMain ()
> > #5 0x0814be1f in main ()
>
> Hm, if you are really lucky, this is because of a corrupt
> pg_internal.init file. Fortunately for you, that's just a cache;
> try removing (all of the) pg_internal.init files and see if the
> DB will start.
>
How do I know which files those are?
I see nothing named that although grep suggests they did exist...
# grep pg_internal.init */*
Binary file base/1 matches
Binary file base/10818 matches
Binary file base/10819 matches
Darren
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-27 05:19:38 | Re: How to reindex when unable to open relation? |
| Previous Message | Phillip Smith | 2008-02-27 04:20:22 | Re: Backup to Tape Incomplete |