Tom Lane wrote:
>
> Michael Simms <grim@argh.demon.co.uk> writes:
> > The postmaster stderr says:
> > FATAL 1: my bits moved right off the end of the world!
>
> Hmm. That error is coming out of the btree index code. Vadim knows
> that code better than anyone else, so he might have something to say
> here, but my past-midnight recollection is that we've seen that error
> being triggered when there are oversize entries in the index (where
> "oversize" = "more than half a disk page"). It's a bug, for sure,
> but what you probably want right now is a workaround. Do you have any
> entries in indexed columns that are over 4K, and can you get rid of them?
This FATAL means that index is broken (some prev insertion
was interrupted by elog(ERROR) or backend crash) - try to rebuild...
WAL should fix this bug.
Vadim
