Re: Bug?: Update on ancestor for a row of a child

From: Kevin Way <kevin(dot)way(at)overtone(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Bug?: Update on ancestor for a row of a child
Date: 2001-09-24 16:11:48
Message-ID: 20010924161148.A23482@bean.overtone.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

> And you think that Oracle is entirely free of bugs? ;-)

Yes, but they'd be exciting technology-oriented e-business enabled bugs!

> Still, I understand your frustration.

Thanks... It's just frustrating that the bug is on something so basic,
which makes it both hard to code around and hard for me to delve into the
postgres source and fix. I spent a few hours tracing source before finally
conceding the point that it takes more than a few hours to understand
postgres internals well enough to fix a major bug.

For development purposes I've just removed all the CHECK constraints
from my child tables, and I'm hoping some genius will solve the problem
by the time I'm looking to deploy.

-Kevin Way

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Way 2001-09-24 16:18:10 Re: [HACKERS] Server crash caused by CHECK on child
Previous Message Stephan Szabo 2001-09-24 16:09:48 Re: Server crash caused by CHECK on child

Browse pgsql-sql by date

  From Date Subject
Next Message Kevin Way 2001-09-24 16:18:10 Re: [HACKERS] Server crash caused by CHECK on child
Previous Message Josh Berkus 2001-09-24 16:10:27 Re: How to enter lists into database:Example.