Skip site navigation (1) Skip section navigation (2)

Server crash caused by CHECK on child

From: Kovacs Baldvin <kb136(at)hszk(dot)bme(dot)hu>
To: <pgsql-hackers(at)postgresql(dot)org>, <pgsql-sql(at)postgresql(dot)org>, Kevin Way <kevin(dot)way(at)overtone(dot)org>
Subject: Server crash caused by CHECK on child
Date: 2001-09-24 08:01:43
Message-ID: Pine.GSO.4.33.0109241000560.5647-100000@ural2 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackerspgsql-sql
-- Hi Kevin, and everyone!
-- 
-- I don't think that I only found a minor bug compared to
-- the other you wrote in your last letter: the backend crash
-- is caused by the same CHECK constraint in the child table.
-- 
-- However, for you without time to analyzing Kevin's huge
-- scheme, here is the very simplified, crash-causing script.
-- 
------------------------------------

drop table child;
drop table ancestor;

create table ancestor (
  node_id int4,
  a int4
);

create table child (
  b int4 NOT NULL DEFAULT 0 ,
  c int4 not null default 3,
  CHECK ( child.b = 0 OR child.b = 1 )
) inherits (ancestor);

insert into ancestor values (3,4);
insert into child (node_id, a, b) values (5,6,1);

update ancestor set a=8 where node_id=5;

---------------------------------
-- 
-- I am hunting it, but I have to learn all what this query-executing
-- about, so probably it takes uncomparable longer for me than for
-- a developer.
-- 
-- Regards,
-- Baldvin
-- 



Responses

pgsql-hackers by date

Next:From: Jean-Michel POUREDate: 2001-09-24 08:53:31
Subject: Re: [HACKERS] UTF-8 support
Previous:From: Dave PageDate: 2001-09-24 07:37:20
Subject: Re: [ODBC] UTF-8 support

pgsql-bugs by date

Next:From: Ana ClaudiaDate: 2001-09-24 09:28:31
Subject:
Previous:From: Billy G. AllieDate: 2001-09-24 06:16:34
Subject: Re: Bug #467: Can't insert a value of 0 (zero) into a Bytea

pgsql-sql by date

Next:From: Oleg OleninDate: 2001-09-24 09:08:51
Subject: How to get BLOB size?
Previous:From: Oleg BartunovDate: 2001-09-24 05:54:11
Subject: Re: loading array_iterator.so does not work with Postgresql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group