Re: [GENERAL] Query Optimizer makes a poor choice

>>On Tue, Nov 29, 2011 at 7:21 PM, Tyler Hains wrote: >> # explain analyze select * from cards where card_set_id=2850 order by >> card_id limit 1; >>   

Re: [GENERAL] Query Optimizer makes a poor choice

>> I haven't had a chance to experiment with the SET STATISTICS, but that >> got me going on something interesting... >> >> Do these statistics look right? >> >> # SELECT attname, n_distinct, most_common_vals, histogram_bounds FROM >> pg_stats WHERE tablename = 'cards'; >> >... >> "card_set_id"  

Re: [GENERAL] Query Optimizer makes a poor choice

On Tue, Nov 29, 2011 at 11:21 AM, Tyler Hains wrote: > # explain analyze select * from cards where card_set_id=2850 order by > card_id limit 1; >    QU

Re: [GENERAL] Query Optimizer makes a poor choice

2011/11/29 Tyler Hains : > # explain analyze select * from cards where card_set_id=2850 order by > card_id limit 1; >    QU

[GENERAL] Query Optimizer makes a poor choice

with our dataset. Is there a better way around this? Tyler Hains IT Director ProfitPoint, Inc. www.profitpointinc.com

Re: [GENERAL] JDBC Postgres problem

> We are having a very strange issue where for certain records, queries > sent via JDBC return no results when the identical query via command > line or pgadmin return non-null (expected) results. Example below. We > are running 8.3.9. We found our problem. It turned out to be a config file that w

[GENERAL] JDBC Postgres problem

me: 0.221 ms Note the 0 rows returned via JDBC. Has anyone ever heard of anything like this before? Thanks, Tyler Hains IT Director ProfitPoint, Inc. www.profitpointinc.com

[GENERAL] Wiki Updates - 9.0

granted to trusted people to keep the info accurate? I’d happily help with general stuff and let people fill in the details – but didn’t see a way to register… Thanks, Tyler Hains ProfitPoint, Inc. www.profitpointinc.com