Re: [HACKERS] Problem with new function - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] Problem with new function
Date
Msg-id m11UAYh-0003kLC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] Problem with new function  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>
> Grzegorz =?iso-8859-2?Q?Prze=BCdziecki?=  <grzegorz_przezdziecki@lupus.waw.pl> writes:
> > in  may log file :
> > Fatal 1 : btree: cannot split if start (2) >= maxoff (2)
> > or somethings like this:
> > fatal 1: my bits moved right off the end of the world!
>
> I think we fixed some bugs in that area in 6.5.2 --- please update
> and see if the problem is still there.

    The  pg_proc_prosrc_index  (causing  this  failure)  is still
    there.  If I  remember  right,  something  on  SQL  functions
    requires  this index to quickly find a particular function BY
    SOURCE. Seems a little screwed up.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: RI and NULL's
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Progress report: buffer refcount bugs and SQL functions