Re: Fwd: Request for error explaination || Adding a new integer in indextupleData Structure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rohit Goyal <rhtgyl(dot)87(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fwd: Request for error explaination || Adding a new integer in indextupleData Structure
Date: 2014-01-27 17:25:42
Message-ID: 10911.1390843542@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-novice

Rohit Goyal <rhtgyl(dot)87(at)gmail(dot)com> writes:
> Hi All,
> I was trying to modify indextupledata structure by adding an integer
> variable. ButI faced an error message "psql: FATAL: could not find tuple
> for opclass 10032".

> Could anyone please help me in resolving this issue.

You broke a system catalog index. Without seeing what you changed and
where, it's impossible to say just how, but that's the bottom line.

In recent versions of PG, opclass 10032 is btree name_ops (unless you've
also added/removed system catalog entries), which is a pretty plausible
thing to be one of the first indexscanned fetches during relcache.c
initialization, so I don't think there's any great significance in this
particular error message. It's likely that you broke *all* indexscans
not just one specific one.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2014-01-27 17:35:06 Re: Planning time in explain/explain analyze
Previous Message Rohit Goyal 2014-01-27 17:05:34 Fwd: Request for error explaination || Adding a new integer in indextupleData Structure

Browse pgsql-novice by date

  From Date Subject
Next Message Daniel Staal 2014-01-27 19:26:05 Re: Update with last known location?
Previous Message Rohit Goyal 2014-01-27 17:05:34 Fwd: Request for error explaination || Adding a new integer in indextupleData Structure