On 1/9/11 3:38 PM, Tom Lane wrote: > 1. Do nothing. The issue seems quite unlikely to affect anyone in the > field, since in fact "use a seqscan" is probably the right answer > anytime reltuples = 1; and anyway using a GIN index for plain equality > is a corner case to begin with. However, it could confuse people who > were doing testing (it confused me!).
+1. It's an unexpected result, but not actually a bad one. It just doesn't seem worth messing with code which works in production just to help testing. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers