My apologies, I meant user_activity_log, and not user_anime_log in the
previous email.
This isn't a huge issue as the query could easily be rewritten using a more
pragmatic join structure, but I thought it would be worth mentioning as
occasionally bugs involve more than just what meets the eye. Th
On Wed, Sep 16, 2009 at 6:39 PM, Kenaniah Cerny wrote:
> I can provide the output of statistics queries if you would like. Just let
> me know which statistics you want and I'll pastebin them.
>
> As far as selectivity goes, the selectivity estimate for the
> user_anime_log.user_account_id was defi
I can provide the output of statistics queries if you would like. Just let
me know which statistics you want and I'll pastebin them.
As far as selectivity goes, the selectivity estimate for the
user_anime_log.user_account_id was definitely miscalculated. The
user_anime_log contains up to 15 entrie
On Tue, Sep 15, 2009 at 11:35 PM, Kenaniah Cerny wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5059
> Logged by: Kenaniah Cerny
> Email address: kenan...@gmail.com
> PostgreSQL version: 8.4.1
> Operating system: Centos5.2
> Description: Planner
The following bug has been logged online:
Bug reference: 5059
Logged by: Kenaniah Cerny
Email address: kenan...@gmail.com
PostgreSQL version: 8.4.1
Operating system: Centos5.2
Description:Planner ignores estimates when planning an IN ()
subquery
Details:
Consider th
