Tom Lane <t...@sss.pgh.pa.us> wrote: > In any case, it is now clear to me that this bug is capable of > eating peoples' databases, as in "what just happened to our most > critical table? Uh, it's not there anymore, boss, but we seem to > have duplicate pg_class entries for this other table". Based on this, I don't think we want to wait for bug reports. One would be too many. +1 for backpatching a fix. > As for it not being the last bug, no, it's probably not. That's a > pretty sucky excuse for not fixing it too. I agree. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
