Re: Bug in RI

Odd, it looks like it had trouble doing the heap_openr
on the relation, although I don't immediately see why...

What does
select * from pg_trigger where
tgconstrname='fk_folders__parent'
give you?

I wasn't able to duplicate with the table statements below
and dummy values. Do you have a subset of your data that
will cause the probably that you can send?

Stephan Szabo
sszabo(at)bigpanda(dot)com

On Thu, 21 Sep 2000, Jeroen van Vianen wrote:

> Hi,
>
> I encountered the following problem:
>
> ./configure --enable-debug --prefix=/opt/postgres
> Edit config.h: BLCKSZ 32768
>
> postgres=# select version();
> version
> ---------------------------------------------------------------
> PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.95.2
> (1 row)
>
> I have the following table:
>
> CREATE TABLE "folders" (
> "nr" int4 NOT NULL,
> "parent" int4,
> "name" character varying(100) NOT NULL,
> "lang" character varying(2) NOT NULL,
> "sort_order" int2 DEFAULT 0 NOT NULL,
> "stylesheet" character varying(100),
> "introduction" character varying(1000),
> "template" character varying(100) NOT NULL,
> "img_normal" character varying(50),
> "img_over" character varying(50),
> "img_active" character varying(50),
> PRIMARY KEY ("nr")
> );
>
> CREATE CONSTRAINT TRIGGER "fk_folders__parent" AFTER INSERT OR UPDATE ON
> "folders" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE
> PROCEDURE "RI_FKey_check_ins" ('fk_folders__parent', 'folders', 'folders',
> 'UNSPECIFIED', 'parent', 'nr');
>
> CREATE CONSTRAINT TRIGGER "fk_folders__parent" AFTER DELETE ON
> "folders" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE
> PROCEDURE "RI_FKey_noaction_del" ('fk_folders__parent', 'folders',
> 'folders', 'UNSPECIFIED', 'parent', 'nr');
>
> CREATE CONSTRAINT TRIGGER "fk_folders__parent" AFTER UPDATE ON
> "folders" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE
> PROCEDURE "RI_FKey_noaction_upd" ('fk_folders__parent', 'folders',
> 'folders', 'UNSPECIFIED', 'parent', 'nr');