Re: Failed assertion on cluster - Mailing list pgsql-hackers

From Larry Rosenman
Subject Re: Failed assertion on cluster
Date
Msg-id Pine.uw2.4.61.0502061115010.2999@lerami.lerctr.org
Whole thread Raw
In response to Failed assertion on cluster  (Larry Rosenman <ler@lerctr.org>)
Responses Re: Failed assertion on cluster
Re: Failed assertion on cluster
List pgsql-hackers
On Sun, 6 Feb 2005, Larry Rosenman wrote:

> I get the following:
>
> $ TRAP: FailedAssertion("!(!(tup->t_data->t_infomask & 0x0010))", File: 
> "heapam.c", Line: 1133)
>
>
> when I try to cluster this table:
>
> CREATE TABLE virtusers (
>    lhs text,
>    rhs text,
>    insert_date timestamp(0) with time zone DEFAULT now(),
>    insert_who text DEFAULT "current_user"(),
>    "comment" text
> );
> ALTER TABLE ONLY virtusers ALTER COLUMN lhs SET STATISTICS 100;
>
> --
> -- Name: vu_lhs_index; Type: INDEX; Schema: public; Owner: ler; Tablespace: 
> --
>
> CREATE UNIQUE INDEX vu_lhs_index ON virtusers USING btree (lhs);
>
>
> ALTER INDEX public.vu_lhs_index OWNER TO ler;
>
>
> When I issue the cluster vu_lhs_index on virtusers, I get the above 
> assertion.
>
> 8.0.1 on UnixWare 7.1.4
>
>
>
I had done the following, which I think is what's doing it:

1) alter table virtusers (and all the others in that db) set without oids;
2) changed postgresql.conf's default_with_oids to false.

Based on my read, this case is what's causing the grief.


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749


pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: Failed assertion on cluster
Next
From: Ron Mayer
Date:
Subject: Re: Query optimizer 8.0.1 (and 8.0)