Here is Tom's comment on the issue.
> Chris Bitmead <chris.bitmead@bigfoot.com> writes:
> > Following is I believe evidence of a pretty bad bug in postgres. This is
> > the 990329 snapshot.
>
> > httpd=> insert into category(name, image, parent) SELECT 'boo', 'boo',
> > oid FROM category* where name = 'foo';
> > INSERT 158370 1
> > httpd=> select * from category;
> > name |image|url|parent
> > --------+-----+---+------
> > foo |foo | | 0
> > bar |bar | |158321
> > Products|.gif | |
> > (3 rows)
>
> > Ok, what's going on here. The 'boo' record did not appear!
>
> Interesting. You'll notice the INSERT response claims that a tuple was
> inserted, and even gives you the OID for it. Wonder where it went?
>
> Anyway, that sure suggests that the SELECT part worked, and the problem
> is that the new tuple got dropped on the floor later. (Or could it have
> been inserted into another table? Are there other tables that category*
> includes?)
>
> I'm guessing this has something to do with Vadim's recent work, but
> I don't pretend to know what's wrong...
>
> regards, tom lane
>
>
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
