Re: sqlsmith crash incremental sort
James Coleman <jtc331@gmail.com>
From: James Coleman <jtc331@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>,
Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-04-18T18:23:25Z
Lists: pgsql-hackers
On Thu, Apr 16, 2020 at 9:26 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Tomas Vondra <tomas.vondra@2ndquadrant.com> writes: > > I think we have essentially three options: > > 1) assuming there's just a single group > > 2) assuming each row is a separate group > > 3) something in between > > If (1) and (2) are worst/best-case scenarios, maybe we should pick > > something in between. We have DEFAULT_NUM_DISTINCT (200) which > > essentially says "we don't know what the number of groups is" so maybe > > we should use that. > > I wouldn't recommend picking either the best or worst cases. > > Possibly DEFAULT_NUM_DISTINCT is a sane choice, though it's fair to > wonder if it's quite applicable to the case where we already know > we've grouped by some columns. Do you think defining a new default, say, DEFAULT_NUM_DISTINCT_PRESORTED is preferred then? And choose some value like "1/2 of the normal DEFAULT_NUM_DISTINCT groups" or some such? James
Commits
-
Simplify cost_incremental_sort a bit
- 60fbb4d76250 13.0 landed
-
Fix cost_incremental_sort for expressions with varno 0
- de0dc1a84710 13.0 landed