stanislaw.skonieczny@gmail.com wrote:
> In our product we have found that PG is choosing full scan on a big table
> instead using indexes.
> This was caused caused by very inaccurate estimations of total number of
> rows in the table.
Stanislaw emailed the -owner address with the attached email.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Bug reference: 14858
I attach sample script to resproduce the problem and it's output.
Stanisław Skonieczny
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
