Re: [HACKERS] Problem with new function

From: wieck(at)debis(dot)com (Jan Wieck)
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: grzegorz_przezdziecki(at)lupus(dot)waw(dot)pl, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Problem with new function
Date: 1999-09-23 15:13:19
Message-ID: m11UAYh-0003kLC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Grzegorz =?iso-8859-2?Q?Prze=BCdziecki?= <grzegorz_przezdziecki(at)lupus(dot)waw(dot)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(at)debis(dot)com (Jan Wieck) #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-09-23 15:28:51 Re: [HACKERS] Progress report: buffer refcount bugs and SQL functions
Previous Message Jan Wieck 1999-09-23 15:07:13 RI and NULL's