Re: pg_stats and range statistics
Gregory Stark (as CFM) <stark.cfm@gmail.com>
From: "Gregory Stark (as CFM)" <stark.cfm@gmail.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Egor Rogov <e.rogov@postgrespro.ru>, Soumyadeep Chakraborty <soumyadeep2007@gmail.com>,
pgsql-hackers@lists.postgresql.org
Date: 2023-03-20T19:27:37Z
Lists: pgsql-hackers
On Sun, 22 Jan 2023 at 18:22, Tomas Vondra <tomas.vondra@enterprisedb.com> wrote: > > I wonder if we have other functions doing something similar, i.e. > accepting a polymorphic type and then imposing additional restrictions > on it. Meh, there's things like array comparison functions that require both arguments to be the same kind of arrays. And array_agg that requires the elements to be the same type as the state array (ie, same type as the first element). Not sure there are any taking just one specific type though. > > Shouldn't this add some sql tests ? > > Yeah, I guess we should have a couple tests calling these functions on > different range arrays. > > This reminds me lower()/upper() have some extra rules about handling > empty ranges / infinite boundaries etc. These functions should behave > consistently (as if we called lower() in a loop) and I'm pretty sure > that's not the current state. Are we still waiting on these two items? Egor, do you think you'll have a chance to work it for this month? -- Gregory Stark As Commitfest Manager
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Collect and use histograms of lower and upper bounds for range types.
- 918eee0c497c 9.3.0 cited