Re: [HACKERS] PostgreSQL v6.4 BETA2 ... - Mailing list pgsql-hackers

From jwieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] PostgreSQL v6.4 BETA2 ...
Date
Msg-id m0zTS8P-000EBRC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] PostgreSQL v6.4 BETA2 ...  (jwieck@debis.com (Jan Wieck))
Responses Re: [HACKERS] PostgreSQL v6.4 BETA2 ...
List pgsql-hackers
That was me:
>
> >
> >
> > I just built and regression tested the current source tree on both Solaris
> > x86 and Solaris Sparc, and other then a few bugs that I've fixed, it was
> > smooth...
> >
> > Any arguments against getting a BETA2 out tomorrow afternoon?
>
>     Have  a crashing backend after a huge transaction on the next
>     insert into a table with indices. Crash is  reproducable  and
>     seems to be due to a corrupted index file.
>
>     Recompiling with COPT=-g now...
>

    Harrr  -  using  text_ops  on  an  int4 field in CREATE INDEX
    doesn't make much sense.

    Bruce, please add 6.5 TODO:

    Parser must check on CREATE INDEX that the opcdeftype of  the
    used  operator  class is compatible with the indexed field or
    the index functions return type.


Jan

--

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

pgsql-hackers by date:

Previous
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] What about LIMIT in SELECT ?
Next
From: Brook Milligan
Date:
Subject: Re: [HACKERS] PostgreSQL v6.4 BETA2 ...