Re: Analyze results in more expensive query plan

2019-05-22 Thread Jeremy Altavilla
; > On Tue, 21 May 2019 at 08:23, Jeremy Altavilla > wrote: > > > > Thanks for the suggestion. I created extended statistics objects for the > > two tables in question. Unfortunately the resulting plan was the same (and > > had the same estimates). It looks like

Re: Analyze results in more expensive query plan

2019-05-20 Thread Jeremy Altavilla
1.00, "1, 2 => 4": 1.00, "1, 4 => 2": 1.00, "2, 4 => 1": 1.00} For bag keys 1, 2, 3 are id, owner_id and bag_type_id. For bag_type 1, 2, 4 are id, name and game. --Thanks --Jeremy On Fri, May 17, 2019 at 9:35 AM Tom Lane wrote: >

Analyze results in more expensive query plan

2019-05-17 Thread Jeremy Altavilla
Hello, We have several select statements whose performance is greatly improved by deleting some stats from pg_statistic. With the stats present the database reaches 100% cpu at 13k queries per second. Without these stats, the same machine can handle over 29k queries per second. We were able rep