pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Server crash caused by CHECK on child
5+ messages / 4 participants
[nested] [flat]

* Server crash caused by CHECK on child
@ 2001-09-24 08:01  Kovacs Baldvin <kb136@hszk.bme.hu>
  0 siblings, 3 replies; 5+ messages in thread

From: Kovacs Baldvin @ 2001-09-24 08:01 UTC (permalink / raw)
  To: pgsql-hackers@postgresql.org; pgsql-sql; Kevin Way <kevin.way@overtone.org>

-- 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
-- 





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Server crash caused by CHECK on child
@ 2001-09-24 11:42  Kevin Way <kevin.way@overtone.org>
  parent: Kovacs Baldvin <kb136@hszk.bme.hu>
  2 siblings, 0 replies; 5+ messages in thread

From: Kevin Way @ 2001-09-24 11:42 UTC (permalink / raw)
  To: Kovacs Baldvin <kb136@hszk.bme.hu>; +Cc: pgsql-sql

> -- 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.

Oooh, my bad.  I should run your scripts before assuming I know how
they fail.

> -- However, for you without time to analyzing Kevin's huge
> -- scheme, here is the very simplified, crash-causing script.

Thank you so much for finding this simplified method of crashing
Postgres.  Hopefully somebody can find a fix now.

> -- 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.

That's my problem as well, though your example is vastly easier to
trace than mine.  

-Kevin Way




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Server crash caused by CHECK on child
@ 2001-09-24 16:09  Stephan Szabo <sszabo@megazone23.bigpanda.com>
  parent: Kovacs Baldvin <kb136@hszk.bme.hu>
  2 siblings, 1 reply; 5+ messages in thread

From: Stephan Szabo @ 2001-09-24 16:09 UTC (permalink / raw)
  To: Kovacs Baldvin <kb136@hszk.bme.hu>; +Cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org, Kevin Way <kevin.way@overtone.org>


What version are you trying this script on?  I'm not
seeing a crash on my 7.2 devel system (and the update occurs).

On Mon, 24 Sep 2001, Kovacs Baldvin wrote:

> -- 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;




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: [HACKERS] Server crash caused by CHECK on child
@ 2001-09-24 16:18  Kevin Way <kevin.way@overtone.org>
  parent: Stephan Szabo <sszabo@megazone23.bigpanda.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Kevin Way @ 2001-09-24 16:18 UTC (permalink / raw)
  To: Stephan Szabo <sszabo@megazone23.bigpanda.com>; +Cc: pgsql-bugs@postgresql.org

> What version are you trying this script on?  I'm not
> seeing a crash on my 7.2 devel system (and the update occurs).

7.1.3.  I'll sup a copy of the 7.2 sources and see if that fixes the test
case, and my actual bug.

-Kevin Way



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Server crash caused by CHECK on child
@ 2001-10-11 20:38  Bruce Momjian <pgman@candle.pha.pa.us>
  parent: Kovacs Baldvin <kb136@hszk.bme.hu>
  2 siblings, 0 replies; 5+ messages in thread

From: Bruce Momjian @ 2001-10-11 20:38 UTC (permalink / raw)
  To: Kovacs Baldvin <kb136@hszk.bme.hu>; +Cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org, Kevin Way <kevin.way@overtone.org>


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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2001-10-11 20:38 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-09-24 08:01 Server crash caused by CHECK on child Kovacs Baldvin <kb136@hszk.bme.hu>
2001-09-24 11:42 ` Kevin Way <kevin.way@overtone.org>
2001-09-24 16:09 ` Stephan Szabo <sszabo@megazone23.bigpanda.com>
2001-09-24 16:18   ` Kevin Way <kevin.way@overtone.org>
2001-10-11 20:38 ` Bruce Momjian <pgman@candle.pha.pa.us>

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