Re: FWD: bug report: index is not a btree

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: FWD: bug report: index is not a btree
Date: 2005-08-03 15:26:26
Message-ID: 1564.1123082786@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Fuhr <mike(at)fuhr(dot)org> writes:
> I can duplicate this in 7.3.10, but only if the postmaster does a
> redo when it restarts. If I do a checkpoint before killing the
> postmaster then the insert succeeds.
> I couldn't duplicate this behavior in 7.4.8, 8.0.3, or HEAD. The
> 7.4 Release Notes have an item about making B-tree indexes fully
> WAL-safe, so I wonder if that fixes the problem.

Yeah. Before 7.4 there was no WAL record emitted for the act of
initializing the btree metapage, so this behavior is pretty much
exactly what you'd expect. It's possible that we could backport
that single change, but if memory serves there were a number of
other ways in which btree index build violated the WAL principle,
so I'm not sure there's much point. You more or less had to
checkpoint to be sure the new index is fully down to disk.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Vahe 2005-08-04 12:19:12 BUG #1805: FATAL: invalid command-line arguments for server process HINT: Try "postgres --help" for more inform
Previous Message Mario Reiley 2005-08-03 13:05:16 BUG #1804: Installations Problems