On Tue, Feb 18, 2014 at 5:56 PM, Peter Geoghegan <p...@heroku.com> wrote: > That was my first suspicion, but then re-indexing didn't help, while > VACUUM FREEZE had the immediate effect of making both plans give a > consistent answer.
I should add that this is an unremarkable int4 primary key (which was dropped and recreated by the customer). There is no obvious reason why we should see wrong answers that are attributable to application code or environment. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
