Why does NULL ordering impact a btree scan in PostgreSQL?
I asked the question in irc, it seems that they just never did it.

&lt; johto&gt; EvanCarroll; "because nobody implemented it" is usually the answer
&lt; macdice&gt; EvanCarroll: we absolutely could implement that and it's been discussed in this channel.  the codez have not been forthcoming
&lt; macdice&gt; an index scan that is smart enough to skip null (start after null) and then skip back to the nulls at the end
&lt; macdice&gt; probably the easiest of many potential skip scans tricks we could teach indexes to do


(pending other potential answers, I'll just accept this)