Alvaro Herrera <alvhe...@2ndquadrant.com> writes: > I'm not quite clear on why the third query, the one in ri_PerformCheck, > is invoking a sequence.
It's not --- SeqNext is the next-tuple function for a sequential scan. Nothing to do with sequences. Now, it *is* worth wondering why the heck a query on the table's primary key is using a seqscan and not an indexscan. Maybe the planner thinks there are just a few rows in the table? But the stack trace seems unexceptional other than that. I'm wondering if the combination of autoexplain and pg_stat_statements is causing trouble. Yeah, it would be real nice to see a self-contained test case for this. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers