pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Kovacs Baldvin <kb136@hszk.bme.hu>
Cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org, Kevin Way <kevin.way@overtone.org>
Subject: Re: Server crash caused by CHECK on child
Date: Thu, 11 Oct 2001 16:38:37 -0400 (EDT)
Message-ID: <200110112038.f9BKcbD10024@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.GSO.4.33.0109241000560.5647-100000@ural2>


I can confirm this now works fine in current sources.  No crash.

> -- 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
> -- 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (5+ messages)

Message-ID: <200110112038.f9BKcbD10024@candle.pha.pa.us>
Permalink:  ../200110112038.f9BKcbD10024@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200110112038.f9BKcbD10024@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: pgman@candle.pha.pa.us, kb136@hszk.bme.hu, kevin.way@overtone.org
  Subject: Re: Server crash caused by CHECK on child
  In-Reply-To: <200110112038.f9BKcbD10024@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox