Planner Row-Count Errors
Multi-column filter conditions lead to poor selectivity estimate
http://archives.postgresql.org/message-id/6960.1309560409@sss.pgh.pa.us
http://archives.postgresql.org/message-id/4EFC2CE0.7050001@beccati.com
http://archives.postgresql.org/message-id/3dee1b02-0be4-4402-94e9-17a74a9e4ec8@zimbra1.ovus.it
http://archives.postgresql.org/message-id/BLU123-W20B062EC217D902A05BAC1F5FD0@phx.gbl
http://archives.postgresql.org/message-id/CAETCRjg_3kp-MniE6ZmEH4ZMSE4xiSD=01vsuXrQae4Yxwq32Q@mail.gmail.com [debatable]
http://www.postgresql.org/message-id/5102A5F7.2070103@gmail.com
Correlations between columns values aren't recognized
ORDER BY + LIMIT
http://archives.postgresql.org/message-id/4E13A9C2.9000906@kc8onw.net
http://archives.postgresql.org/message-id/4E1C8E62.2090800@megafon.hr
http://archives.postgresql.org/message-id/6B8FADC8-9692-439F-8AA4-0CAA287FCEB0@me.com
http://archives.postgresql.org/message-id/4EDE717A.9050604@megafon.hr
http://archives.postgresql.org/message-id/4F61A909.20109@gmail.com
http://archives.postgresql.org/message-id/A0211EA5A93846FE9F6504F8676905ED@gmail.com
http://www.postgresql.org/message-id/51686787.3050308@optionshouse.com
http://www.postgresql.org/message-id/2583.1365866479@sss.pgh.pa.us
http://archives.postgresql.org/message-id/19B2B4ECC4724A438200C54257BA8B20@gmail.com
http://archives.postgresql.org/message-id/4205A216-5AD0-4F23-826F-542537B27E62@skype.net
Can't See Through WITH
http://archives.postgresql.org/message-id/339959BC-3A27-4269-8A3E-4C157EBABB86@tripadvisor.com
http://archives.postgresql.org/message-id/Prayer.1.3.4.1110102259170.8390@hermes-2.csi.cam.ac.uk
http://archives.postgresql.org/message-id/24672.1319561025@sss.pgh.pa.us
http://archives.postgresql.org/message-id/COL116-W19C19E568788169715A9A7A3F40@phx.gbl
Generic plans can suck
http://archives.postgresql.org/message-id/1327440846.1968.20.camel@tony1.localdomain
http://archives.postgresql.org/message-id/m3mx4eys6o.fsf@mnc.ch
http://archives.postgresql.org/message-id/201302220925.26460.msc@antzsystem.de
Selectivity estimates on arbitrary expressions are poor
http://archives.postgresql.org/message-id/4EE8E161.1090702@digsys.bg
http://www.postgresql.org/message-id/5118E977.7050109@objectdata.com.br
Join selectivity doesn't know about cross-table correlations
http://www.postgresql.org/message-id/50D2171D.9010608@gmail.com
Uncommitted tuples don't affect statistics
http://archives.postgresql.org/message-id/5179E77B.7050601@catalyst.net.nz
http://www.postgresql.org/message-id/273CF8C2-159B-44FF-B382-61A76541F435@gmail.com
Histogram bounds can slide due to new data [Fixed]
http://archives.postgresql.org/message-id/1322922869210-5044616.post@n5.nabble.com
Inheritance parents aren't assumed to be completely empty [Fixed]
http://archives.postgresql.org/message-id/7806.1310233430@sss.pgh.pa.us
no stats for WITH RECURSIVE
GROUP BY output has no statistics
http://archives.postgresql.org/message-id/iv8b4r$2q83$1@news.hub.org
redundant equality constraints not identified as such
IN/NOT IN estimation doesn't assume array elements are distinct [fixed in 9.2]