Re: [HACKERS] Re: ERROR: index_rescan: invalid amrescan regproc ???

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter T Mount <peter(at)retep(dot)org(dot)uk>
Cc: Brian P Millett <bpm(at)ec-group(dot)com>, postgres <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Re: ERROR: index_rescan: invalid amrescan regproc ???
Date: 1999-04-24 17:46:54
Message-ID: 24164.924976014@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter T Mount <peter(at)retep(dot)org(dot)uk> writes:
> On Fri, 23 Apr 1999, Brian P Millett wrote:
>> At this point I get a SQLException: "Fastpath: index_rescan: invalid
>> amrescan regproc"

> This looks like something in the backend has died while a fastpath
> function was being used. I'll see if I can recreate it here.

Just to save you repeating the look-around I just did: that's
coming out of backend/access/index/indexam.c, and it's apparently
complaining that a pg_am table row has a null amrescan field.
That shouldn't be true of any of the pg_am rows in a correct
installation.

Brian, what does 'select * from pg_am' show? Did you do an initdb
while installing the 6.5 snapshot you're using?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message JP Rosevear 1999-04-24 22:28:58 [Fwd: [HACKERS] typeidTypeRelid Error]
Previous Message Tom Lane 1999-04-24 15:46:13 Re: [HACKERS] Can't start postmaster