DROP TABLE... CASCADE weirdness

Hackers,

Suppose I do

CREATE TABLE a (a int);
CREATE TABLE b () INHERITS (a);

And then I want to drop both tables:

regression=# DROP TABLE a, b;
NOTICE: table b depends on table a
ERROR: Cannot drop table a because other objects depend on it
Use DROP ... CASCADE to drop the dependent objects too

Oh, so I use CASCADE:

regression=# DROP TABLE a, b CASCADE;
NOTICE: Drop cascades to table b
ERROR: table "b" does not exist

I understand what's going on and how to get the desired behavior, but
it's weird and I think it should be fixed if possible.

--
Alvaro Herrera (<alvherre[a]atentus.com>)
"Endurecerse, pero jamas perder la ternura" (E. Guevara)