Re: ERROR: failed to add item to the index page

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andreas Joseph Krogh <andreas(at)visena(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: ERROR: failed to add item to the index page
Date: 2019-04-30 13:43:16
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andreas Joseph Krogh <andreas(at)visena(dot)com> writes:
> With master (3dbb317d32f4f084ef7badaed8ef36f5c9b85fe6) I'm getting this:
> visena=# CREATE INDEX origo_email_part_hdrvl_value_idx ON
> public.origo_email_part_headervalue USING btree
> (lower(substr((header_value)::text, 0, 1000)) varchar_pattern_ops);
> psql: ERROR: failed to add item to the index page

Hm, your example works for me on HEAD.

Usually, the first thing to suspect when you're tracking HEAD and get
bizarre failures is that you have a messed-up build. Before spending
any time diagnosing more carefully, do "make distclean", reconfigure,
rebuild, reinstall, then see if problem is still there.

(In theory, you can avoid this sort of failure with appropriate use
of --enable-depend, but personally I don't trust that too much.
I find that with ccache + autoconf cache + parallel build, rebuilding
completely is fast enough that it's something I just do routinely
after any git pull. I'd rather use up my remaining brain cells on
other kinds of problems...)

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2019-04-30 13:46:28 Re: [PATCH v4] Add \warn to psql
Previous Message Michael Banck 2019-04-30 13:07:43 Re: [Patch] Base backups and random or zero pageheaders