From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
cc: Ron <ronljohnsonjr@gmail.com>, pgsql-admin@lists.postgresql.org
Subject: Re: Very slow 101-feeling design/query..
In-reply-to: 
 <CAOC+FBXFtjELi+HrQiL+oNySrTeVz-g3te1a3Jr97iC+VCrxWw@mail.gmail.com>
References: 
 <CAOC+FBWG-0BH_prvkbMTFuAQ37pr+Kx3S=V=krE1qkGhojXtJw@mail.gmail.com>
 <144f1205-22cc-b6ef-b0f9-21c7d271397a@gmail.com>
 <CAOC+FBXFtjELi+HrQiL+oNySrTeVz-g3te1a3Jr97iC+VCrxWw@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Fri, 10 Dec 2021 15:27:58 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <13147.1639191413.1@sss.pgh.pa.us>
Date: Fri, 10 Dec 2021 21:56:53 -0500
Message-ID: <13148.1639191413@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/13148.1639191413%40sss.pgh.pa.us>
Precedence: bulk

Wells Oliver <wells.oliver@gmail.com> writes:
> PG 13.4. Can't quite run the EXPLAIN ANALYZE since it takes so long, but
> EXPLAIN SELECT DISTINCT game_id FROM vw_joints shows (s = joints, p = plays)

I doubt you're going to get a query plan that's significantly better
than what you show here.  But those tables are pretty large, so
I wonder whether you have cranked up work_mem.

One potential issue is that the planner thinks there are only
about 1829 distinct game_id values:

>  HashAggregate  (cost=63810150.11..63810168.40 rows=1829 width=4)
>    Group Key: p.game_id

Is that about the right size of result for this?

			regards, tom lane