"Dickson S. Guedes" <lis...@guedesoft.net> writes:
> I could reproduce this once in a database that already have a table
> named "t", then after i did dropped it i couldn't anymore.
As noted, you might have to force use of a hash join (my machine
preferred a mergejoin before the ANALYZE and a nestloop after).
It's definitely broken :-(
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
