From: Kevin Way <kevin.way@overtone.org>
To: Kovacs Baldvin <kb136@hszk.bme.hu>
Cc: pgsql-sql@postgresql.org
Subject: Re: Server crash caused by CHECK on child
Date: Mon, 24 Sep 2001 11:42:33 +0000
Message-ID: <20010924114233.A76269@bean.overtone.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0109241000560.5647-100000@ural2>
References: <Pine.GSO.4.33.0109241000560.5647-100000@ural2>
> -- 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
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: kevin.way@overtone.org, kb136@hszk.bme.hu
Subject: Re: Server crash caused by CHECK on child
In-Reply-To: <20010924114233.A76269@bean.overtone.org>
* 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