| From: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [7.0.2] cannot create an index ... |
| Date: | 2000-10-10 04:32:12 |
| Message-ID: | Pine.BSF.4.21.0010100030590.23541-100000@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 10 Oct 2000, Tom Lane wrote:
> "Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> > TRAP: Failed Assertion("!(metaopaque->btpo_flags & (1 << 3)):", File: "nbtpage.c
> > ", Line: 181)
>
> Hmm. That suggests a clobbered index (as in, first page zeroed out).
> The Assert report doesn't tell us which index. Possibly a backtrace
> of the corefile would help.
I've rebuilt the whole data structure, as I fear it is a residual of the
crash we had last week, but, if it means anytyhing, we had done a 'drop
database/create database' before we tried to rebuild teh database ... is
it possible that the pg_log got corrupted and could affect this? or maybe
template1, so that when the create database was run, it was pulling in
corrupted system tables?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-10 04:36:17 | Re: [7.0.2] cannot create an index ... |
| Previous Message | Tom Lane | 2000-10-10 04:25:02 | Re: [7.0.2] cannot create an index ... |