1997-04-27 13:40:13 -04:00
|
|
|
--
|
|
|
|
|
-- AGGREGATES
|
|
|
|
|
--
|
2000-01-05 12:32:29 -05:00
|
|
|
|
2022-02-08 15:30:38 -05:00
|
|
|
-- directory paths are passed to us in environment variables
|
|
|
|
|
\getenv abs_srcdir PG_ABS_SRCDIR
|
|
|
|
|
|
Change floating-point output format for improved performance.
Previously, floating-point output was done by rounding to a specific
decimal precision; by default, to 6 or 15 decimal digits (losing
information) or as requested using extra_float_digits. Drivers that
wanted exact float values, and applications like pg_dump that must
preserve values exactly, set extra_float_digits=3 (or sometimes 2 for
historical reasons, though this isn't enough for float4).
Unfortunately, decimal rounded output is slow enough to become a
noticable bottleneck when dealing with large result sets or COPY of
large tables when many floating-point values are involved.
Floating-point output can be done much faster when the output is not
rounded to a specific decimal length, but rather is chosen as the
shortest decimal representation that is closer to the original float
value than to any other value representable in the same precision. The
recently published Ryu algorithm by Ulf Adams is both relatively
simple and remarkably fast.
Accordingly, change float4out/float8out to output shortest decimal
representations if extra_float_digits is greater than 0, and make that
the new default. Applications that need rounded output can set
extra_float_digits back to 0 or below, and take the resulting
performance hit.
We make one concession to portability for systems with buggy
floating-point input: we do not output decimal values that fall
exactly halfway between adjacent representable binary values (which
would rely on the reader doing round-to-nearest-even correctly). This
is known to be a problem at least for VS2013 on Windows.
Our version of the Ryu code originates from
https://github.com/ulfjack/ryu/ at commit c9c3fb1979, but with the
following (significant) modifications:
- Output format is changed to use fixed-point notation for small
exponents, as printf would, and also to use lowercase 'e', a
minimum of 2 exponent digits, and a mandatory sign on the exponent,
to keep the formatting as close as possible to previous output.
- The output of exact midpoint values is disabled as noted above.
- The integer fast-path code is changed somewhat (since we have
fixed-point output and the upstream did not).
- Our project style has been largely applied to the code with the
exception of C99 declaration-after-statement, which has been
retained as an exception to our present policy.
- Most of upstream's debugging and conditionals are removed, and we
use our own configure tests to determine things like uint128
availability.
Changing the float output format obviously affects a number of
regression tests. This patch uses an explicit setting of
extra_float_digits=0 for test output that is not expected to be
exactly reproducible (e.g. due to numerical instability or differing
algorithms for transcendental functions).
Conversions from floats to numeric are unchanged by this patch. These
may appear in index expressions and it is not yet clear whether any
change should be made, so that can be left for another day.
This patch assumes that the only supported floating point format is
now IEEE format, and the documentation is updated to reflect that.
Code by me, adapting the work of Ulf Adams and other contributors.
References:
https://dl.acm.org/citation.cfm?id=3192369
Reviewed-by: Tom Lane, Andres Freund, Donald Dong
Discussion: https://postgr.es/m/87r2el1bx6.fsf@news-spur.riddles.org.uk
2019-02-13 10:20:33 -05:00
|
|
|
-- avoid bit-exact output here because operations may not be bit-exact.
|
|
|
|
|
SET extra_float_digits = 0;
|
|
|
|
|
|
2022-02-08 15:30:38 -05:00
|
|
|
-- prepare some test data
|
|
|
|
|
CREATE TABLE aggtest (
|
|
|
|
|
a int2,
|
|
|
|
|
b float4
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
\set filename :abs_srcdir '/data/agg.data'
|
|
|
|
|
COPY aggtest FROM :'filename';
|
|
|
|
|
|
|
|
|
|
ANALYZE aggtest;
|
|
|
|
|
|
|
|
|
|
|
1997-04-27 13:40:13 -04:00
|
|
|
SELECT avg(four) AS avg_1 FROM onek;
|
|
|
|
|
|
1997-04-29 10:29:16 -04:00
|
|
|
SELECT avg(a) AS avg_32 FROM aggtest WHERE a < 100;
|
1997-04-27 13:40:13 -04:00
|
|
|
|
2023-02-22 03:32:12 -05:00
|
|
|
SELECT any_value(v) FROM (VALUES (1), (2), (3)) AS v (v);
|
|
|
|
|
SELECT any_value(v) FROM (VALUES (NULL)) AS v (v);
|
|
|
|
|
SELECT any_value(v) FROM (VALUES (NULL), (1), (2)) AS v (v);
|
|
|
|
|
SELECT any_value(v) FROM (VALUES (array['hello', 'world'])) AS v (v);
|
|
|
|
|
|
2000-07-16 23:05:41 -04:00
|
|
|
-- In 7.1, avg(float4) is computed using float8 arithmetic.
|
|
|
|
|
-- Round the result to 3 digits to avoid platform-specific results.
|
|
|
|
|
|
|
|
|
|
SELECT avg(b)::numeric(10,3) AS avg_107_943 FROM aggtest;
|
1997-04-27 13:40:13 -04:00
|
|
|
|
2000-06-10 01:19:26 -04:00
|
|
|
SELECT avg(gpa) AS avg_3_4 FROM ONLY student;
|
1997-04-27 13:40:13 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
SELECT sum(four) AS sum_1500 FROM onek;
|
|
|
|
|
SELECT sum(a) AS sum_198 FROM aggtest;
|
|
|
|
|
SELECT sum(b) AS avg_431_773 FROM aggtest;
|
2000-06-10 01:19:26 -04:00
|
|
|
SELECT sum(gpa) AS avg_6_8 FROM ONLY student;
|
1997-04-27 13:40:13 -04:00
|
|
|
|
|
|
|
|
SELECT max(four) AS max_3 FROM onek;
|
|
|
|
|
SELECT max(a) AS max_100 FROM aggtest;
|
|
|
|
|
SELECT max(aggtest.b) AS max_324_78 FROM aggtest;
|
|
|
|
|
SELECT max(student.gpa) AS max_3_7 FROM student;
|
|
|
|
|
|
2006-03-10 15:15:28 -05:00
|
|
|
SELECT stddev_pop(b) FROM aggtest;
|
|
|
|
|
SELECT stddev_samp(b) FROM aggtest;
|
|
|
|
|
SELECT var_pop(b) FROM aggtest;
|
|
|
|
|
SELECT var_samp(b) FROM aggtest;
|
1997-04-27 13:40:13 -04:00
|
|
|
|
2006-03-10 15:15:28 -05:00
|
|
|
SELECT stddev_pop(b::numeric) FROM aggtest;
|
|
|
|
|
SELECT stddev_samp(b::numeric) FROM aggtest;
|
|
|
|
|
SELECT var_pop(b::numeric) FROM aggtest;
|
|
|
|
|
SELECT var_samp(b::numeric) FROM aggtest;
|
|
|
|
|
|
|
|
|
|
-- population variance is defined for a single tuple, sample variance
|
|
|
|
|
-- is not
|
Fix behavior of float aggregates for single Inf or NaN inputs.
When there is just one non-null input value, and it is infinity or NaN,
aggregates such as stddev_pop and covar_pop should produce a NaN
result, because the calculation is not well-defined. They used to do
so, but since we adopted Youngs-Cramer aggregation in commit e954a727f,
they produced zero instead. That's an oversight, so fix it. Add tests
exercising these edge cases.
Affected aggregates are
var_pop(double precision)
stddev_pop(double precision)
var_pop(real)
stddev_pop(real)
regr_sxx(double precision,double precision)
regr_syy(double precision,double precision)
regr_sxy(double precision,double precision)
regr_r2(double precision,double precision)
regr_slope(double precision,double precision)
regr_intercept(double precision,double precision)
covar_pop(double precision,double precision)
corr(double precision,double precision)
Back-patch to v12 where the behavior change was accidentally introduced.
Report and patch by me; thanks to Dean Rasheed for review.
Discussion: https://postgr.es/m/353062.1591898766@sss.pgh.pa.us
2020-06-13 13:43:24 -04:00
|
|
|
SELECT var_pop(1.0::float8), var_samp(2.0::float8);
|
|
|
|
|
SELECT stddev_pop(3.0::float8), stddev_samp(4.0::float8);
|
|
|
|
|
SELECT var_pop('inf'::float8), var_samp('inf'::float8);
|
|
|
|
|
SELECT stddev_pop('inf'::float8), stddev_samp('inf'::float8);
|
|
|
|
|
SELECT var_pop('nan'::float8), var_samp('nan'::float8);
|
|
|
|
|
SELECT stddev_pop('nan'::float8), stddev_samp('nan'::float8);
|
|
|
|
|
SELECT var_pop(1.0::float4), var_samp(2.0::float4);
|
|
|
|
|
SELECT stddev_pop(3.0::float4), stddev_samp(4.0::float4);
|
|
|
|
|
SELECT var_pop('inf'::float4), var_samp('inf'::float4);
|
|
|
|
|
SELECT stddev_pop('inf'::float4), stddev_samp('inf'::float4);
|
|
|
|
|
SELECT var_pop('nan'::float4), var_samp('nan'::float4);
|
|
|
|
|
SELECT stddev_pop('nan'::float4), stddev_samp('nan'::float4);
|
|
|
|
|
SELECT var_pop(1.0::numeric), var_samp(2.0::numeric);
|
2006-03-10 15:15:28 -05:00
|
|
|
SELECT stddev_pop(3.0::numeric), stddev_samp(4.0::numeric);
|
2020-07-22 19:19:44 -04:00
|
|
|
SELECT var_pop('inf'::numeric), var_samp('inf'::numeric);
|
|
|
|
|
SELECT stddev_pop('inf'::numeric), stddev_samp('inf'::numeric);
|
Fix behavior of float aggregates for single Inf or NaN inputs.
When there is just one non-null input value, and it is infinity or NaN,
aggregates such as stddev_pop and covar_pop should produce a NaN
result, because the calculation is not well-defined. They used to do
so, but since we adopted Youngs-Cramer aggregation in commit e954a727f,
they produced zero instead. That's an oversight, so fix it. Add tests
exercising these edge cases.
Affected aggregates are
var_pop(double precision)
stddev_pop(double precision)
var_pop(real)
stddev_pop(real)
regr_sxx(double precision,double precision)
regr_syy(double precision,double precision)
regr_sxy(double precision,double precision)
regr_r2(double precision,double precision)
regr_slope(double precision,double precision)
regr_intercept(double precision,double precision)
covar_pop(double precision,double precision)
corr(double precision,double precision)
Back-patch to v12 where the behavior change was accidentally introduced.
Report and patch by me; thanks to Dean Rasheed for review.
Discussion: https://postgr.es/m/353062.1591898766@sss.pgh.pa.us
2020-06-13 13:43:24 -04:00
|
|
|
SELECT var_pop('nan'::numeric), var_samp('nan'::numeric);
|
|
|
|
|
SELECT stddev_pop('nan'::numeric), stddev_samp('nan'::numeric);
|
1997-04-27 13:40:13 -04:00
|
|
|
|
2024-07-11 11:50:50 -04:00
|
|
|
-- verify correct results for min(record) and max(record) aggregates
|
|
|
|
|
SELECT max(row(a,b)) FROM aggtest;
|
|
|
|
|
SELECT max(row(b,a)) FROM aggtest;
|
|
|
|
|
SELECT min(row(a,b)) FROM aggtest;
|
|
|
|
|
SELECT min(row(b,a)) FROM aggtest;
|
|
|
|
|
|
Improve performance of numeric sum(), avg(), stddev(), variance(), etc.
This patch improves performance of most built-in aggregates that formerly
used a NUMERIC or NUMERIC array as their transition type; this includes
not only aggregates on numeric inputs, but some aggregates on integer
inputs where overflow of an int8 value is a possibility. The code now
uses a special-purpose data structure to avoid array construction and
deconstruction overhead, as well as packing and unpacking overhead for
numeric values.
These aggregates' transition type is now declared as INTERNAL, since
it doesn't correspond to any SQL data type. To keep the planner from
thinking that that means a lot of storage will be used, we make use
of the just-added pg_aggregate.aggtransspace feature. The space estimate
is set to 128 bytes, which is at least in the right ballpark.
Hadi Moshayedi, reviewed by Pavel Stehule and Tomas Vondra
2013-11-16 18:46:34 -05:00
|
|
|
-- verify correct results for null and NaN inputs
|
|
|
|
|
select sum(null::int4) from generate_series(1,3);
|
|
|
|
|
select sum(null::int8) from generate_series(1,3);
|
|
|
|
|
select sum(null::numeric) from generate_series(1,3);
|
|
|
|
|
select sum(null::float8) from generate_series(1,3);
|
|
|
|
|
select avg(null::int4) from generate_series(1,3);
|
|
|
|
|
select avg(null::int8) from generate_series(1,3);
|
|
|
|
|
select avg(null::numeric) from generate_series(1,3);
|
|
|
|
|
select avg(null::float8) from generate_series(1,3);
|
|
|
|
|
select sum('NaN'::numeric) from generate_series(1,3);
|
|
|
|
|
select avg('NaN'::numeric) from generate_series(1,3);
|
|
|
|
|
|
2018-10-06 06:20:09 -04:00
|
|
|
-- verify correct results for infinite inputs
|
2020-07-22 19:19:44 -04:00
|
|
|
SELECT sum(x::float8), avg(x::float8), var_pop(x::float8)
|
2018-10-06 06:20:09 -04:00
|
|
|
FROM (VALUES ('1'), ('infinity')) v(x);
|
2020-07-22 19:19:44 -04:00
|
|
|
SELECT sum(x::float8), avg(x::float8), var_pop(x::float8)
|
2018-10-06 06:20:09 -04:00
|
|
|
FROM (VALUES ('infinity'), ('1')) v(x);
|
2020-07-22 19:19:44 -04:00
|
|
|
SELECT sum(x::float8), avg(x::float8), var_pop(x::float8)
|
2018-10-06 06:20:09 -04:00
|
|
|
FROM (VALUES ('infinity'), ('infinity')) v(x);
|
2020-07-22 19:19:44 -04:00
|
|
|
SELECT sum(x::float8), avg(x::float8), var_pop(x::float8)
|
|
|
|
|
FROM (VALUES ('-infinity'), ('infinity')) v(x);
|
|
|
|
|
SELECT sum(x::float8), avg(x::float8), var_pop(x::float8)
|
|
|
|
|
FROM (VALUES ('-infinity'), ('-infinity')) v(x);
|
|
|
|
|
SELECT sum(x::numeric), avg(x::numeric), var_pop(x::numeric)
|
|
|
|
|
FROM (VALUES ('1'), ('infinity')) v(x);
|
|
|
|
|
SELECT sum(x::numeric), avg(x::numeric), var_pop(x::numeric)
|
|
|
|
|
FROM (VALUES ('infinity'), ('1')) v(x);
|
|
|
|
|
SELECT sum(x::numeric), avg(x::numeric), var_pop(x::numeric)
|
|
|
|
|
FROM (VALUES ('infinity'), ('infinity')) v(x);
|
|
|
|
|
SELECT sum(x::numeric), avg(x::numeric), var_pop(x::numeric)
|
2018-10-06 06:20:09 -04:00
|
|
|
FROM (VALUES ('-infinity'), ('infinity')) v(x);
|
2020-07-22 19:19:44 -04:00
|
|
|
SELECT sum(x::numeric), avg(x::numeric), var_pop(x::numeric)
|
|
|
|
|
FROM (VALUES ('-infinity'), ('-infinity')) v(x);
|
2018-10-06 06:20:09 -04:00
|
|
|
|
|
|
|
|
-- test accuracy with a large input offset
|
|
|
|
|
SELECT avg(x::float8), var_pop(x::float8)
|
|
|
|
|
FROM (VALUES (100000003), (100000004), (100000006), (100000007)) v(x);
|
|
|
|
|
SELECT avg(x::float8), var_pop(x::float8)
|
|
|
|
|
FROM (VALUES (7000000000005), (7000000000007)) v(x);
|
|
|
|
|
|
2006-07-28 14:33:04 -04:00
|
|
|
-- SQL2003 binary aggregates
|
|
|
|
|
SELECT regr_count(b, a) FROM aggtest;
|
|
|
|
|
SELECT regr_sxx(b, a) FROM aggtest;
|
|
|
|
|
SELECT regr_syy(b, a) FROM aggtest;
|
|
|
|
|
SELECT regr_sxy(b, a) FROM aggtest;
|
|
|
|
|
SELECT regr_avgx(b, a), regr_avgy(b, a) FROM aggtest;
|
|
|
|
|
SELECT regr_r2(b, a) FROM aggtest;
|
|
|
|
|
SELECT regr_slope(b, a), regr_intercept(b, a) FROM aggtest;
|
|
|
|
|
SELECT covar_pop(b, a), covar_samp(b, a) FROM aggtest;
|
|
|
|
|
SELECT corr(b, a) FROM aggtest;
|
|
|
|
|
|
Fix behavior of float aggregates for single Inf or NaN inputs.
When there is just one non-null input value, and it is infinity or NaN,
aggregates such as stddev_pop and covar_pop should produce a NaN
result, because the calculation is not well-defined. They used to do
so, but since we adopted Youngs-Cramer aggregation in commit e954a727f,
they produced zero instead. That's an oversight, so fix it. Add tests
exercising these edge cases.
Affected aggregates are
var_pop(double precision)
stddev_pop(double precision)
var_pop(real)
stddev_pop(real)
regr_sxx(double precision,double precision)
regr_syy(double precision,double precision)
regr_sxy(double precision,double precision)
regr_r2(double precision,double precision)
regr_slope(double precision,double precision)
regr_intercept(double precision,double precision)
covar_pop(double precision,double precision)
corr(double precision,double precision)
Back-patch to v12 where the behavior change was accidentally introduced.
Report and patch by me; thanks to Dean Rasheed for review.
Discussion: https://postgr.es/m/353062.1591898766@sss.pgh.pa.us
2020-06-13 13:43:24 -04:00
|
|
|
-- check single-tuple behavior
|
|
|
|
|
SELECT covar_pop(1::float8,2::float8), covar_samp(3::float8,4::float8);
|
|
|
|
|
SELECT covar_pop(1::float8,'inf'::float8), covar_samp(3::float8,'inf'::float8);
|
|
|
|
|
SELECT covar_pop(1::float8,'nan'::float8), covar_samp(3::float8,'nan'::float8);
|
|
|
|
|
|
2018-10-06 06:20:09 -04:00
|
|
|
-- test accum and combine functions directly
|
|
|
|
|
CREATE TABLE regr_test (x float8, y float8);
|
|
|
|
|
INSERT INTO regr_test VALUES (10,150),(20,250),(30,350),(80,540),(100,200);
|
|
|
|
|
SELECT count(*), sum(x), regr_sxx(y,x), sum(y),regr_syy(y,x), regr_sxy(y,x)
|
|
|
|
|
FROM regr_test WHERE x IN (10,20,30,80);
|
|
|
|
|
SELECT count(*), sum(x), regr_sxx(y,x), sum(y),regr_syy(y,x), regr_sxy(y,x)
|
|
|
|
|
FROM regr_test;
|
|
|
|
|
SELECT float8_accum('{4,140,2900}'::float8[], 100);
|
|
|
|
|
SELECT float8_regr_accum('{4,140,2900,1290,83075,15050}'::float8[], 200, 100);
|
|
|
|
|
SELECT count(*), sum(x), regr_sxx(y,x), sum(y),regr_syy(y,x), regr_sxy(y,x)
|
|
|
|
|
FROM regr_test WHERE x IN (10,20,30);
|
|
|
|
|
SELECT count(*), sum(x), regr_sxx(y,x), sum(y),regr_syy(y,x), regr_sxy(y,x)
|
|
|
|
|
FROM regr_test WHERE x IN (80,100);
|
|
|
|
|
SELECT float8_combine('{3,60,200}'::float8[], '{0,0,0}'::float8[]);
|
|
|
|
|
SELECT float8_combine('{0,0,0}'::float8[], '{2,180,200}'::float8[]);
|
|
|
|
|
SELECT float8_combine('{3,60,200}'::float8[], '{2,180,200}'::float8[]);
|
|
|
|
|
SELECT float8_regr_combine('{3,60,200,750,20000,2000}'::float8[],
|
|
|
|
|
'{0,0,0,0,0,0}'::float8[]);
|
|
|
|
|
SELECT float8_regr_combine('{0,0,0,0,0,0}'::float8[],
|
|
|
|
|
'{2,180,200,740,57800,-3400}'::float8[]);
|
|
|
|
|
SELECT float8_regr_combine('{3,60,200,750,20000,2000}'::float8[],
|
|
|
|
|
'{2,180,200,740,57800,-3400}'::float8[]);
|
|
|
|
|
DROP TABLE regr_test;
|
|
|
|
|
|
|
|
|
|
-- test count, distinct
|
2006-03-10 15:15:28 -05:00
|
|
|
SELECT count(four) AS cnt_1000 FROM onek;
|
1999-12-12 20:27:21 -05:00
|
|
|
SELECT count(DISTINCT four) AS cnt_4 FROM onek;
|
|
|
|
|
|
2002-11-20 19:42:20 -05:00
|
|
|
select ten, count(*), sum(four) from onek
|
|
|
|
|
group by ten order by ten;
|
1999-12-12 20:27:21 -05:00
|
|
|
|
2002-11-20 19:42:20 -05:00
|
|
|
select ten, count(four), sum(DISTINCT four) from onek
|
|
|
|
|
group by ten order by ten;
|
1999-12-12 20:27:21 -05:00
|
|
|
|
2006-07-27 15:52:07 -04:00
|
|
|
-- user-defined aggregates
|
1997-04-27 13:40:13 -04:00
|
|
|
SELECT newavg(four) AS avg_1 FROM onek;
|
|
|
|
|
SELECT newsum(four) AS sum_1500 FROM onek;
|
|
|
|
|
SELECT newcnt(four) AS cnt_1000 FROM onek;
|
2006-07-27 15:52:07 -04:00
|
|
|
SELECT newcnt(*) AS cnt_1000 FROM onek;
|
|
|
|
|
SELECT oldcnt(*) AS cnt_1000 FROM onek;
|
|
|
|
|
SELECT sum2(q1,q2) FROM int8_tbl;
|
2003-06-06 11:04:03 -04:00
|
|
|
|
|
|
|
|
-- test for outer-level aggregates
|
|
|
|
|
|
|
|
|
|
-- this should work
|
|
|
|
|
select ten, sum(distinct four) from onek a
|
|
|
|
|
group by ten
|
|
|
|
|
having exists (select 1 from onek b where sum(distinct a.four) = b.four);
|
|
|
|
|
|
|
|
|
|
-- this should fail because subquery has an agg of its own in WHERE
|
|
|
|
|
select ten, sum(distinct four) from onek a
|
|
|
|
|
group by ten
|
|
|
|
|
having exists (select 1 from onek b
|
|
|
|
|
where sum(distinct a.four + b.four) = b.four);
|
2004-05-26 11:26:28 -04:00
|
|
|
|
2009-04-25 12:44:56 -04:00
|
|
|
-- Test handling of sublinks within outer-level aggregates.
|
|
|
|
|
-- Per bug report from Daniel Grace.
|
|
|
|
|
select
|
|
|
|
|
(select max((select i.unique2 from tenk1 i where i.unique1 = o.unique1)))
|
|
|
|
|
from tenk1 o;
|
|
|
|
|
|
2016-08-24 14:37:50 -04:00
|
|
|
-- Test handling of Params within aggregate arguments in hashed aggregation.
|
|
|
|
|
-- Per bug report from Jeevan Chalke.
|
|
|
|
|
explain (verbose, costs off)
|
|
|
|
|
select s1, s2, sm
|
|
|
|
|
from generate_series(1, 3) s1,
|
|
|
|
|
lateral (select s2, sum(s1 + s2) sm
|
|
|
|
|
from generate_series(1, 3) s2 group by s2) ss
|
|
|
|
|
order by 1, 2;
|
|
|
|
|
select s1, s2, sm
|
|
|
|
|
from generate_series(1, 3) s1,
|
|
|
|
|
lateral (select s2, sum(s1 + s2) sm
|
|
|
|
|
from generate_series(1, 3) s2 group by s2) ss
|
|
|
|
|
order by 1, 2;
|
|
|
|
|
|
|
|
|
|
explain (verbose, costs off)
|
|
|
|
|
select array(select sum(x+y) s
|
|
|
|
|
from generate_series(1,3) y group by y order by s)
|
|
|
|
|
from generate_series(1,3) x;
|
|
|
|
|
select array(select sum(x+y) s
|
|
|
|
|
from generate_series(1,3) y group by y order by s)
|
|
|
|
|
from generate_series(1,3) x;
|
|
|
|
|
|
2004-05-26 11:26:28 -04:00
|
|
|
--
|
|
|
|
|
-- test for bitwise integer aggregates
|
|
|
|
|
--
|
|
|
|
|
CREATE TEMPORARY TABLE bitwise_test(
|
|
|
|
|
i2 INT2,
|
|
|
|
|
i4 INT4,
|
|
|
|
|
i8 INT8,
|
|
|
|
|
i INTEGER,
|
|
|
|
|
x INT2,
|
|
|
|
|
y BIT(4)
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
-- empty case
|
2010-11-23 15:27:50 -05:00
|
|
|
SELECT
|
2004-05-26 11:26:28 -04:00
|
|
|
BIT_AND(i2) AS "?",
|
2021-03-06 13:25:45 -05:00
|
|
|
BIT_OR(i4) AS "?",
|
|
|
|
|
BIT_XOR(i8) AS "?"
|
2004-05-26 11:26:28 -04:00
|
|
|
FROM bitwise_test;
|
|
|
|
|
|
|
|
|
|
COPY bitwise_test FROM STDIN NULL 'null';
|
|
|
|
|
1 1 1 1 1 B0101
|
|
|
|
|
3 3 3 null 2 B0100
|
|
|
|
|
7 7 7 3 4 B1100
|
|
|
|
|
\.
|
|
|
|
|
|
|
|
|
|
SELECT
|
|
|
|
|
BIT_AND(i2) AS "1",
|
|
|
|
|
BIT_AND(i4) AS "1",
|
|
|
|
|
BIT_AND(i8) AS "1",
|
|
|
|
|
BIT_AND(i) AS "?",
|
|
|
|
|
BIT_AND(x) AS "0",
|
|
|
|
|
BIT_AND(y) AS "0100",
|
|
|
|
|
|
|
|
|
|
BIT_OR(i2) AS "7",
|
|
|
|
|
BIT_OR(i4) AS "7",
|
|
|
|
|
BIT_OR(i8) AS "7",
|
|
|
|
|
BIT_OR(i) AS "?",
|
|
|
|
|
BIT_OR(x) AS "7",
|
2021-03-06 13:25:45 -05:00
|
|
|
BIT_OR(y) AS "1101",
|
|
|
|
|
|
|
|
|
|
BIT_XOR(i2) AS "5",
|
|
|
|
|
BIT_XOR(i4) AS "5",
|
|
|
|
|
BIT_XOR(i8) AS "5",
|
|
|
|
|
BIT_XOR(i) AS "?",
|
|
|
|
|
BIT_XOR(x) AS "7",
|
|
|
|
|
BIT_XOR(y) AS "1101"
|
2004-05-26 11:26:28 -04:00
|
|
|
FROM bitwise_test;
|
|
|
|
|
|
|
|
|
|
--
|
|
|
|
|
-- test boolean aggregates
|
|
|
|
|
--
|
|
|
|
|
-- first test all possible transition and final states
|
|
|
|
|
|
|
|
|
|
SELECT
|
|
|
|
|
-- boolean and transitions
|
|
|
|
|
-- null because strict
|
|
|
|
|
booland_statefunc(NULL, NULL) IS NULL AS "t",
|
|
|
|
|
booland_statefunc(TRUE, NULL) IS NULL AS "t",
|
|
|
|
|
booland_statefunc(FALSE, NULL) IS NULL AS "t",
|
|
|
|
|
booland_statefunc(NULL, TRUE) IS NULL AS "t",
|
|
|
|
|
booland_statefunc(NULL, FALSE) IS NULL AS "t",
|
|
|
|
|
-- and actual computations
|
|
|
|
|
booland_statefunc(TRUE, TRUE) AS "t",
|
|
|
|
|
NOT booland_statefunc(TRUE, FALSE) AS "t",
|
|
|
|
|
NOT booland_statefunc(FALSE, TRUE) AS "t",
|
|
|
|
|
NOT booland_statefunc(FALSE, FALSE) AS "t";
|
|
|
|
|
|
|
|
|
|
SELECT
|
|
|
|
|
-- boolean or transitions
|
|
|
|
|
-- null because strict
|
|
|
|
|
boolor_statefunc(NULL, NULL) IS NULL AS "t",
|
|
|
|
|
boolor_statefunc(TRUE, NULL) IS NULL AS "t",
|
|
|
|
|
boolor_statefunc(FALSE, NULL) IS NULL AS "t",
|
|
|
|
|
boolor_statefunc(NULL, TRUE) IS NULL AS "t",
|
|
|
|
|
boolor_statefunc(NULL, FALSE) IS NULL AS "t",
|
|
|
|
|
-- actual computations
|
|
|
|
|
boolor_statefunc(TRUE, TRUE) AS "t",
|
|
|
|
|
boolor_statefunc(TRUE, FALSE) AS "t",
|
|
|
|
|
boolor_statefunc(FALSE, TRUE) AS "t",
|
|
|
|
|
NOT boolor_statefunc(FALSE, FALSE) AS "t";
|
|
|
|
|
|
2010-11-23 15:27:50 -05:00
|
|
|
CREATE TEMPORARY TABLE bool_test(
|
2004-05-26 11:26:28 -04:00
|
|
|
b1 BOOL,
|
|
|
|
|
b2 BOOL,
|
|
|
|
|
b3 BOOL,
|
|
|
|
|
b4 BOOL);
|
|
|
|
|
|
|
|
|
|
-- empty case
|
|
|
|
|
SELECT
|
|
|
|
|
BOOL_AND(b1) AS "n",
|
|
|
|
|
BOOL_OR(b3) AS "n"
|
|
|
|
|
FROM bool_test;
|
|
|
|
|
|
|
|
|
|
COPY bool_test FROM STDIN NULL 'null';
|
|
|
|
|
TRUE null FALSE null
|
|
|
|
|
FALSE TRUE null null
|
|
|
|
|
null TRUE FALSE null
|
|
|
|
|
\.
|
|
|
|
|
|
|
|
|
|
SELECT
|
|
|
|
|
BOOL_AND(b1) AS "f",
|
|
|
|
|
BOOL_AND(b2) AS "t",
|
|
|
|
|
BOOL_AND(b3) AS "f",
|
|
|
|
|
BOOL_AND(b4) AS "n",
|
|
|
|
|
BOOL_AND(NOT b2) AS "f",
|
|
|
|
|
BOOL_AND(NOT b3) AS "t"
|
|
|
|
|
FROM bool_test;
|
|
|
|
|
|
|
|
|
|
SELECT
|
|
|
|
|
EVERY(b1) AS "f",
|
|
|
|
|
EVERY(b2) AS "t",
|
|
|
|
|
EVERY(b3) AS "f",
|
|
|
|
|
EVERY(b4) AS "n",
|
|
|
|
|
EVERY(NOT b2) AS "f",
|
|
|
|
|
EVERY(NOT b3) AS "t"
|
|
|
|
|
FROM bool_test;
|
|
|
|
|
|
|
|
|
|
SELECT
|
|
|
|
|
BOOL_OR(b1) AS "t",
|
|
|
|
|
BOOL_OR(b2) AS "t",
|
|
|
|
|
BOOL_OR(b3) AS "f",
|
|
|
|
|
BOOL_OR(b4) AS "n",
|
|
|
|
|
BOOL_OR(NOT b2) AS "f",
|
|
|
|
|
BOOL_OR(NOT b3) AS "t"
|
|
|
|
|
FROM bool_test;
|
2005-04-11 19:06:57 -04:00
|
|
|
|
|
|
|
|
--
|
2010-11-04 12:01:17 -04:00
|
|
|
-- Test cases that should be optimized into indexscans instead of
|
|
|
|
|
-- the generic aggregate implementation.
|
2005-04-11 19:06:57 -04:00
|
|
|
--
|
|
|
|
|
|
|
|
|
|
-- Basic cases
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select min(unique1) from tenk1;
|
|
|
|
|
select min(unique1) from tenk1;
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique1) from tenk1;
|
2005-04-11 19:06:57 -04:00
|
|
|
select max(unique1) from tenk1;
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique1) from tenk1 where unique1 < 42;
|
2005-04-11 19:06:57 -04:00
|
|
|
select max(unique1) from tenk1 where unique1 < 42;
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique1) from tenk1 where unique1 > 42;
|
2005-04-11 19:06:57 -04:00
|
|
|
select max(unique1) from tenk1 where unique1 > 42;
|
2016-07-01 11:43:19 -04:00
|
|
|
|
|
|
|
|
-- the planner may choose a generic aggregate here if parallel query is
|
|
|
|
|
-- enabled, since that plan will be parallel safe and the "optimized"
|
|
|
|
|
-- plan, which has almost identical cost, will not be. we want to test
|
|
|
|
|
-- the optimized plan, so temporarily disable parallel query.
|
|
|
|
|
begin;
|
|
|
|
|
set local max_parallel_workers_per_gather = 0;
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique1) from tenk1 where unique1 > 42000;
|
2005-04-11 19:06:57 -04:00
|
|
|
select max(unique1) from tenk1 where unique1 > 42000;
|
2016-07-01 11:43:19 -04:00
|
|
|
rollback;
|
2005-04-11 19:06:57 -04:00
|
|
|
|
|
|
|
|
-- multi-column index (uses tenk1_thous_tenthous)
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(tenthous) from tenk1 where thousand = 33;
|
2005-04-11 19:06:57 -04:00
|
|
|
select max(tenthous) from tenk1 where thousand = 33;
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select min(tenthous) from tenk1 where thousand = 33;
|
2005-04-11 19:06:57 -04:00
|
|
|
select min(tenthous) from tenk1 where thousand = 33;
|
|
|
|
|
|
|
|
|
|
-- check parameter propagation into an indexscan subquery
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select f1, (select min(unique1) from tenk1 where unique1 > f1) AS gt
|
|
|
|
|
from int4_tbl;
|
2005-04-11 19:06:57 -04:00
|
|
|
select f1, (select min(unique1) from tenk1 where unique1 > f1) AS gt
|
2010-11-04 12:01:17 -04:00
|
|
|
from int4_tbl;
|
2008-03-31 12:59:26 -04:00
|
|
|
|
|
|
|
|
-- check some cases that were handled incorrectly in 8.3.0
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select distinct max(unique2) from tenk1;
|
2008-03-31 12:59:26 -04:00
|
|
|
select distinct max(unique2) from tenk1;
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique2) from tenk1 order by 1;
|
2008-03-31 12:59:26 -04:00
|
|
|
select max(unique2) from tenk1 order by 1;
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique2) from tenk1 order by max(unique2);
|
2008-03-31 12:59:26 -04:00
|
|
|
select max(unique2) from tenk1 order by max(unique2);
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique2) from tenk1 order by max(unique2)+1;
|
2008-03-31 12:59:26 -04:00
|
|
|
select max(unique2) from tenk1 order by max(unique2)+1;
|
2010-11-04 12:01:17 -04:00
|
|
|
explain (costs off)
|
|
|
|
|
select max(unique2), generate_series(1,3) as g from tenk1 order by g desc;
|
2008-03-31 12:59:26 -04:00
|
|
|
select max(unique2), generate_series(1,3) as g from tenk1 order by g desc;
|
2010-11-04 12:01:17 -04:00
|
|
|
|
2016-06-28 10:43:11 -04:00
|
|
|
-- interesting corner case: constant gets optimized into a seqscan
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select max(100) from tenk1;
|
|
|
|
|
select max(100) from tenk1;
|
|
|
|
|
|
2010-11-04 12:01:17 -04:00
|
|
|
-- try it on an inheritance tree
|
|
|
|
|
create table minmaxtest(f1 int);
|
|
|
|
|
create table minmaxtest1() inherits (minmaxtest);
|
|
|
|
|
create table minmaxtest2() inherits (minmaxtest);
|
2011-03-22 00:34:31 -04:00
|
|
|
create table minmaxtest3() inherits (minmaxtest);
|
2010-11-04 12:01:17 -04:00
|
|
|
create index minmaxtesti on minmaxtest(f1);
|
|
|
|
|
create index minmaxtest1i on minmaxtest1(f1);
|
|
|
|
|
create index minmaxtest2i on minmaxtest2(f1 desc);
|
2011-03-22 00:34:31 -04:00
|
|
|
create index minmaxtest3i on minmaxtest3(f1) where f1 is not null;
|
2010-11-04 12:01:17 -04:00
|
|
|
|
|
|
|
|
insert into minmaxtest values(11), (12);
|
|
|
|
|
insert into minmaxtest1 values(13), (14);
|
|
|
|
|
insert into minmaxtest2 values(15), (16);
|
2011-03-22 00:34:31 -04:00
|
|
|
insert into minmaxtest3 values(17), (18);
|
2010-11-04 12:01:17 -04:00
|
|
|
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select min(f1), max(f1) from minmaxtest;
|
|
|
|
|
select min(f1), max(f1) from minmaxtest;
|
|
|
|
|
|
2012-11-26 12:57:17 -05:00
|
|
|
-- DISTINCT doesn't do anything useful here, but it shouldn't fail
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select distinct min(f1), max(f1) from minmaxtest;
|
|
|
|
|
select distinct min(f1), max(f1) from minmaxtest;
|
|
|
|
|
|
2010-11-04 12:01:17 -04:00
|
|
|
drop table minmaxtest cascade;
|
2009-12-15 12:57:48 -05:00
|
|
|
|
2024-05-18 14:26:05 -04:00
|
|
|
-- DISTINCT can also trigger wrong answers with hash aggregation (bug #18465)
|
|
|
|
|
begin;
|
|
|
|
|
set local enable_sort = off;
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select f1, (select distinct min(t1.f1) from int4_tbl t1 where t1.f1 = t0.f1)
|
|
|
|
|
from int4_tbl t0;
|
|
|
|
|
select f1, (select distinct min(t1.f1) from int4_tbl t1 where t1.f1 = t0.f1)
|
|
|
|
|
from int4_tbl t0;
|
|
|
|
|
rollback;
|
|
|
|
|
|
Centralize the logic for detecting misplaced aggregates, window funcs, etc.
Formerly we relied on checking after-the-fact to see if an expression
contained aggregates, window functions, or sub-selects when it shouldn't.
This is grotty, easily forgotten (indeed, we had forgotten to teach
DefineIndex about rejecting window functions), and none too efficient
since it requires extra traversals of the parse tree. To improve matters,
define an enum type that classifies all SQL sub-expressions, store it in
ParseState to show what kind of expression we are currently parsing, and
make transformAggregateCall, transformWindowFuncCall, and transformSubLink
check the expression type and throw error if the type indicates the
construct is disallowed. This allows removal of a large number of ad-hoc
checks scattered around the code base. The enum type is sufficiently
fine-grained that we can still produce error messages of at least the
same specificity as before.
Bringing these error checks together revealed that we'd been none too
consistent about phrasing of the error messages, so standardize the wording
a bit.
Also, rewrite checking of aggregate arguments so that it requires only one
traversal of the arguments, rather than up to three as before.
In passing, clean up some more comments left over from add_missing_from
support, and annotate some tests that I think are dead code now that that's
gone. (I didn't risk actually removing said dead code, though.)
2012-08-10 11:35:33 -04:00
|
|
|
-- check for correct detection of nested-aggregate errors
|
|
|
|
|
select max(min(unique1)) from tenk1;
|
|
|
|
|
select (select max(min(unique1)) from int8_tbl) from tenk1;
|
2023-03-13 12:40:28 -04:00
|
|
|
select avg((select avg(a1.col1 order by (select avg(a2.col2) from tenk1 a3))
|
|
|
|
|
from tenk1 a1(col1)))
|
|
|
|
|
from tenk1 a2(col2);
|
Centralize the logic for detecting misplaced aggregates, window funcs, etc.
Formerly we relied on checking after-the-fact to see if an expression
contained aggregates, window functions, or sub-selects when it shouldn't.
This is grotty, easily forgotten (indeed, we had forgotten to teach
DefineIndex about rejecting window functions), and none too efficient
since it requires extra traversals of the parse tree. To improve matters,
define an enum type that classifies all SQL sub-expressions, store it in
ParseState to show what kind of expression we are currently parsing, and
make transformAggregateCall, transformWindowFuncCall, and transformSubLink
check the expression type and throw error if the type indicates the
construct is disallowed. This allows removal of a large number of ad-hoc
checks scattered around the code base. The enum type is sufficiently
fine-grained that we can still produce error messages of at least the
same specificity as before.
Bringing these error checks together revealed that we'd been none too
consistent about phrasing of the error messages, so standardize the wording
a bit.
Also, rewrite checking of aggregate arguments so that it requires only one
traversal of the arguments, rather than up to three as before.
In passing, clean up some more comments left over from add_missing_from
support, and annotate some tests that I think are dead code now that that's
gone. (I didn't risk actually removing said dead code, though.)
2012-08-10 11:35:33 -04:00
|
|
|
|
2016-02-11 17:34:59 -05:00
|
|
|
--
|
|
|
|
|
-- Test removal of redundant GROUP BY columns
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
create temp table t1 (a int, b int, c int, d int, primary key (a, b));
|
|
|
|
|
create temp table t2 (x int, y int, z int, primary key (x, y));
|
|
|
|
|
create temp table t3 (a int, b int, c int, primary key(a, b) deferrable);
|
|
|
|
|
|
|
|
|
|
-- Non-primary-key columns can be removed from GROUP BY
|
|
|
|
|
explain (costs off) select * from t1 group by a,b,c,d;
|
|
|
|
|
|
|
|
|
|
-- No removal can happen if the complete PK is not present in GROUP BY
|
|
|
|
|
explain (costs off) select a,c from t1 group by a,c,d;
|
|
|
|
|
|
|
|
|
|
-- Test removal across multiple relations
|
|
|
|
|
explain (costs off) select *
|
|
|
|
|
from t1 inner join t2 on t1.a = t2.x and t1.b = t2.y
|
|
|
|
|
group by t1.a,t1.b,t1.c,t1.d,t2.x,t2.y,t2.z;
|
|
|
|
|
|
|
|
|
|
-- Test case where t1 can be optimized but not t2
|
|
|
|
|
explain (costs off) select t1.*,t2.x,t2.z
|
|
|
|
|
from t1 inner join t2 on t1.a = t2.x and t1.b = t2.y
|
|
|
|
|
group by t1.a,t1.b,t1.c,t1.d,t2.x,t2.z;
|
|
|
|
|
|
|
|
|
|
-- Cannot optimize when PK is deferrable
|
|
|
|
|
explain (costs off) select * from t3 group by a,b,c;
|
|
|
|
|
|
2019-07-03 07:44:54 -04:00
|
|
|
create temp table t1c () inherits (t1);
|
|
|
|
|
|
|
|
|
|
-- Ensure we don't remove any columns when t1 has a child table
|
|
|
|
|
explain (costs off) select * from t1 group by a,b,c,d;
|
|
|
|
|
|
|
|
|
|
-- Okay to remove columns if we're only querying the parent.
|
|
|
|
|
explain (costs off) select * from only t1 group by a,b,c,d;
|
|
|
|
|
|
|
|
|
|
create temp table p_t1 (
|
|
|
|
|
a int,
|
|
|
|
|
b int,
|
|
|
|
|
c int,
|
|
|
|
|
d int,
|
|
|
|
|
primary key(a,b)
|
|
|
|
|
) partition by list(a);
|
|
|
|
|
create temp table p_t1_1 partition of p_t1 for values in(1);
|
|
|
|
|
create temp table p_t1_2 partition of p_t1 for values in(2);
|
|
|
|
|
|
|
|
|
|
-- Ensure we can remove non-PK columns for partitioned tables.
|
|
|
|
|
explain (costs off) select * from p_t1 group by a,b,c,d;
|
|
|
|
|
|
2025-02-18 06:42:22 -05:00
|
|
|
create unique index t2_z_uidx on t2(z);
|
Detect redundant GROUP BY columns using UNIQUE indexes
d4c3a156c added support that when the GROUP BY contained all of the
columns belonging to a relation's PRIMARY KEY, all other columns
belonging to that relation would be removed from the GROUP BY clause.
That's possible because all other columns are functionally dependent on
the PRIMARY KEY and those columns alone ensure the groups are distinct.
Here we expand on that optimization and allow it to work for any unique
indexes on the table rather than just the PRIMARY KEY index. This
normally requires that all columns in the index are defined with NOT NULL,
however, we can relax that requirement when the index is defined with
NULLS NOT DISTINCT.
When there are multiple suitable indexes to allow columns to be removed,
we prefer the index with the least number of columns as this allows us
to remove the highest number of GROUP BY columns. One day, we may want to
revisit that decision as it may make more sense to use the narrower set of
columns in terms of the width of the data types and stored/queried data.
This also adjusts the code to make use of RelOptInfo.indexlist rather
than looking up the catalog tables.
In passing, add another short-circuit path to allow bailing out earlier
in cases where it's certainly not possible to remove redundant GROUP BY
columns. This early exit is now cheaper to do than when this code was
originally written as 00b41463c made it cheaper to check for empty
Bitmapsets.
Patch originally by Zhang Mingli and later worked on by jian he, but after
I (David) worked on it, there was very little of the original left.
Author: Zhang Mingli, jian he, David Rowley
Reviewed-by: jian he, Andrei Lepikhov
Discussion: https://postgr.es/m/327990c8-b9b2-4b0c-bffb-462249f82de0%40Spark
2024-12-11 21:28:38 -05:00
|
|
|
|
|
|
|
|
-- Ensure we don't remove any columns from the GROUP BY for a unique
|
|
|
|
|
-- index on a NULLable column.
|
2025-02-18 06:42:22 -05:00
|
|
|
explain (costs off) select y,z from t2 group by y,z;
|
Detect redundant GROUP BY columns using UNIQUE indexes
d4c3a156c added support that when the GROUP BY contained all of the
columns belonging to a relation's PRIMARY KEY, all other columns
belonging to that relation would be removed from the GROUP BY clause.
That's possible because all other columns are functionally dependent on
the PRIMARY KEY and those columns alone ensure the groups are distinct.
Here we expand on that optimization and allow it to work for any unique
indexes on the table rather than just the PRIMARY KEY index. This
normally requires that all columns in the index are defined with NOT NULL,
however, we can relax that requirement when the index is defined with
NULLS NOT DISTINCT.
When there are multiple suitable indexes to allow columns to be removed,
we prefer the index with the least number of columns as this allows us
to remove the highest number of GROUP BY columns. One day, we may want to
revisit that decision as it may make more sense to use the narrower set of
columns in terms of the width of the data types and stored/queried data.
This also adjusts the code to make use of RelOptInfo.indexlist rather
than looking up the catalog tables.
In passing, add another short-circuit path to allow bailing out earlier
in cases where it's certainly not possible to remove redundant GROUP BY
columns. This early exit is now cheaper to do than when this code was
originally written as 00b41463c made it cheaper to check for empty
Bitmapsets.
Patch originally by Zhang Mingli and later worked on by jian he, but after
I (David) worked on it, there was very little of the original left.
Author: Zhang Mingli, jian he, David Rowley
Reviewed-by: jian he, Andrei Lepikhov
Discussion: https://postgr.es/m/327990c8-b9b2-4b0c-bffb-462249f82de0%40Spark
2024-12-11 21:28:38 -05:00
|
|
|
|
|
|
|
|
-- Make the column NOT NULL and ensure we remove the redundant column
|
2025-02-18 06:42:22 -05:00
|
|
|
alter table t2 alter column z set not null;
|
|
|
|
|
explain (costs off) select y,z from t2 group by y,z;
|
Detect redundant GROUP BY columns using UNIQUE indexes
d4c3a156c added support that when the GROUP BY contained all of the
columns belonging to a relation's PRIMARY KEY, all other columns
belonging to that relation would be removed from the GROUP BY clause.
That's possible because all other columns are functionally dependent on
the PRIMARY KEY and those columns alone ensure the groups are distinct.
Here we expand on that optimization and allow it to work for any unique
indexes on the table rather than just the PRIMARY KEY index. This
normally requires that all columns in the index are defined with NOT NULL,
however, we can relax that requirement when the index is defined with
NULLS NOT DISTINCT.
When there are multiple suitable indexes to allow columns to be removed,
we prefer the index with the least number of columns as this allows us
to remove the highest number of GROUP BY columns. One day, we may want to
revisit that decision as it may make more sense to use the narrower set of
columns in terms of the width of the data types and stored/queried data.
This also adjusts the code to make use of RelOptInfo.indexlist rather
than looking up the catalog tables.
In passing, add another short-circuit path to allow bailing out earlier
in cases where it's certainly not possible to remove redundant GROUP BY
columns. This early exit is now cheaper to do than when this code was
originally written as 00b41463c made it cheaper to check for empty
Bitmapsets.
Patch originally by Zhang Mingli and later worked on by jian he, but after
I (David) worked on it, there was very little of the original left.
Author: Zhang Mingli, jian he, David Rowley
Reviewed-by: jian he, Andrei Lepikhov
Discussion: https://postgr.es/m/327990c8-b9b2-4b0c-bffb-462249f82de0%40Spark
2024-12-11 21:28:38 -05:00
|
|
|
|
|
|
|
|
-- When there are multiple supporting unique indexes and the GROUP BY contains
|
|
|
|
|
-- columns to cover all of those, ensure we pick the index with the least
|
|
|
|
|
-- number of columns so that we can remove more columns from the GROUP BY.
|
2025-02-18 06:42:22 -05:00
|
|
|
explain (costs off) select x,y,z from t2 group by x,y,z;
|
Detect redundant GROUP BY columns using UNIQUE indexes
d4c3a156c added support that when the GROUP BY contained all of the
columns belonging to a relation's PRIMARY KEY, all other columns
belonging to that relation would be removed from the GROUP BY clause.
That's possible because all other columns are functionally dependent on
the PRIMARY KEY and those columns alone ensure the groups are distinct.
Here we expand on that optimization and allow it to work for any unique
indexes on the table rather than just the PRIMARY KEY index. This
normally requires that all columns in the index are defined with NOT NULL,
however, we can relax that requirement when the index is defined with
NULLS NOT DISTINCT.
When there are multiple suitable indexes to allow columns to be removed,
we prefer the index with the least number of columns as this allows us
to remove the highest number of GROUP BY columns. One day, we may want to
revisit that decision as it may make more sense to use the narrower set of
columns in terms of the width of the data types and stored/queried data.
This also adjusts the code to make use of RelOptInfo.indexlist rather
than looking up the catalog tables.
In passing, add another short-circuit path to allow bailing out earlier
in cases where it's certainly not possible to remove redundant GROUP BY
columns. This early exit is now cheaper to do than when this code was
originally written as 00b41463c made it cheaper to check for empty
Bitmapsets.
Patch originally by Zhang Mingli and later worked on by jian he, but after
I (David) worked on it, there was very little of the original left.
Author: Zhang Mingli, jian he, David Rowley
Reviewed-by: jian he, Andrei Lepikhov
Discussion: https://postgr.es/m/327990c8-b9b2-4b0c-bffb-462249f82de0%40Spark
2024-12-11 21:28:38 -05:00
|
|
|
|
|
|
|
|
-- As above but try ordering the columns differently to ensure we get the
|
|
|
|
|
-- same result.
|
2025-02-18 06:42:22 -05:00
|
|
|
explain (costs off) select x,y,z from t2 group by z,x,y;
|
Detect redundant GROUP BY columns using UNIQUE indexes
d4c3a156c added support that when the GROUP BY contained all of the
columns belonging to a relation's PRIMARY KEY, all other columns
belonging to that relation would be removed from the GROUP BY clause.
That's possible because all other columns are functionally dependent on
the PRIMARY KEY and those columns alone ensure the groups are distinct.
Here we expand on that optimization and allow it to work for any unique
indexes on the table rather than just the PRIMARY KEY index. This
normally requires that all columns in the index are defined with NOT NULL,
however, we can relax that requirement when the index is defined with
NULLS NOT DISTINCT.
When there are multiple suitable indexes to allow columns to be removed,
we prefer the index with the least number of columns as this allows us
to remove the highest number of GROUP BY columns. One day, we may want to
revisit that decision as it may make more sense to use the narrower set of
columns in terms of the width of the data types and stored/queried data.
This also adjusts the code to make use of RelOptInfo.indexlist rather
than looking up the catalog tables.
In passing, add another short-circuit path to allow bailing out earlier
in cases where it's certainly not possible to remove redundant GROUP BY
columns. This early exit is now cheaper to do than when this code was
originally written as 00b41463c made it cheaper to check for empty
Bitmapsets.
Patch originally by Zhang Mingli and later worked on by jian he, but after
I (David) worked on it, there was very little of the original left.
Author: Zhang Mingli, jian he, David Rowley
Reviewed-by: jian he, Andrei Lepikhov
Discussion: https://postgr.es/m/327990c8-b9b2-4b0c-bffb-462249f82de0%40Spark
2024-12-11 21:28:38 -05:00
|
|
|
|
|
|
|
|
-- Ensure we don't use a partial index as proof of functional dependency
|
2025-02-18 06:42:22 -05:00
|
|
|
drop index t2_z_uidx;
|
|
|
|
|
create index t2_z_uidx on t2 (z) where z > 0;
|
|
|
|
|
explain (costs off) select y,z from t2 group by y,z;
|
Detect redundant GROUP BY columns using UNIQUE indexes
d4c3a156c added support that when the GROUP BY contained all of the
columns belonging to a relation's PRIMARY KEY, all other columns
belonging to that relation would be removed from the GROUP BY clause.
That's possible because all other columns are functionally dependent on
the PRIMARY KEY and those columns alone ensure the groups are distinct.
Here we expand on that optimization and allow it to work for any unique
indexes on the table rather than just the PRIMARY KEY index. This
normally requires that all columns in the index are defined with NOT NULL,
however, we can relax that requirement when the index is defined with
NULLS NOT DISTINCT.
When there are multiple suitable indexes to allow columns to be removed,
we prefer the index with the least number of columns as this allows us
to remove the highest number of GROUP BY columns. One day, we may want to
revisit that decision as it may make more sense to use the narrower set of
columns in terms of the width of the data types and stored/queried data.
This also adjusts the code to make use of RelOptInfo.indexlist rather
than looking up the catalog tables.
In passing, add another short-circuit path to allow bailing out earlier
in cases where it's certainly not possible to remove redundant GROUP BY
columns. This early exit is now cheaper to do than when this code was
originally written as 00b41463c made it cheaper to check for empty
Bitmapsets.
Patch originally by Zhang Mingli and later worked on by jian he, but after
I (David) worked on it, there was very little of the original left.
Author: Zhang Mingli, jian he, David Rowley
Reviewed-by: jian he, Andrei Lepikhov
Discussion: https://postgr.es/m/327990c8-b9b2-4b0c-bffb-462249f82de0%40Spark
2024-12-11 21:28:38 -05:00
|
|
|
|
|
|
|
|
-- A unique index defined as NULLS NOT DISTINCT does not need a supporting NOT
|
|
|
|
|
-- NULL constraint on the indexed columns. Ensure the redundant columns are
|
|
|
|
|
-- removed from the GROUP BY for such a table.
|
2025-02-18 06:42:22 -05:00
|
|
|
drop index t2_z_uidx;
|
|
|
|
|
alter table t2 alter column z drop not null;
|
|
|
|
|
create unique index t2_z_uidx on t2(z) nulls not distinct;
|
|
|
|
|
explain (costs off) select y,z from t2 group by y,z;
|
Detect redundant GROUP BY columns using UNIQUE indexes
d4c3a156c added support that when the GROUP BY contained all of the
columns belonging to a relation's PRIMARY KEY, all other columns
belonging to that relation would be removed from the GROUP BY clause.
That's possible because all other columns are functionally dependent on
the PRIMARY KEY and those columns alone ensure the groups are distinct.
Here we expand on that optimization and allow it to work for any unique
indexes on the table rather than just the PRIMARY KEY index. This
normally requires that all columns in the index are defined with NOT NULL,
however, we can relax that requirement when the index is defined with
NULLS NOT DISTINCT.
When there are multiple suitable indexes to allow columns to be removed,
we prefer the index with the least number of columns as this allows us
to remove the highest number of GROUP BY columns. One day, we may want to
revisit that decision as it may make more sense to use the narrower set of
columns in terms of the width of the data types and stored/queried data.
This also adjusts the code to make use of RelOptInfo.indexlist rather
than looking up the catalog tables.
In passing, add another short-circuit path to allow bailing out earlier
in cases where it's certainly not possible to remove redundant GROUP BY
columns. This early exit is now cheaper to do than when this code was
originally written as 00b41463c made it cheaper to check for empty
Bitmapsets.
Patch originally by Zhang Mingli and later worked on by jian he, but after
I (David) worked on it, there was very little of the original left.
Author: Zhang Mingli, jian he, David Rowley
Reviewed-by: jian he, Andrei Lepikhov
Discussion: https://postgr.es/m/327990c8-b9b2-4b0c-bffb-462249f82de0%40Spark
2024-12-11 21:28:38 -05:00
|
|
|
|
2019-07-03 07:44:54 -04:00
|
|
|
drop table t1 cascade;
|
2016-02-11 17:34:59 -05:00
|
|
|
drop table t2;
|
|
|
|
|
drop table t3;
|
2019-07-03 07:44:54 -04:00
|
|
|
drop table p_t1;
|
2016-02-11 17:34:59 -05:00
|
|
|
|
2020-01-01 19:31:41 -05:00
|
|
|
--
|
|
|
|
|
-- Test GROUP BY matching of join columns that are type-coerced due to USING
|
|
|
|
|
--
|
|
|
|
|
|
Make Vars be outer-join-aware.
Traditionally we used the same Var struct to represent the value
of a table column everywhere in parse and plan trees. This choice
predates our support for SQL outer joins, and it's really a pretty
bad idea with outer joins, because the Var's value can depend on
where it is in the tree: it might go to NULL above an outer join.
So expression nodes that are equal() per equalfuncs.c might not
represent the same value, which is a huge correctness hazard for
the planner.
To improve this, decorate Var nodes with a bitmapset showing
which outer joins (identified by RTE indexes) may have nulled
them at the point in the parse tree where the Var appears.
This allows us to trust that equal() Vars represent the same value.
A certain amount of klugery is still needed to cope with cases
where we re-order two outer joins, but it's possible to make it
work without sacrificing that core principle. PlaceHolderVars
receive similar decoration for the same reason.
In the planner, we include these outer join bitmapsets into the relids
that an expression is considered to depend on, and in consequence also
add outer-join relids to the relids of join RelOptInfos. This allows
us to correctly perceive whether an expression can be calculated above
or below a particular outer join.
This change affects FDWs that want to plan foreign joins. They *must*
follow suit when labeling foreign joins in order to match with the
core planner, but for many purposes (if postgres_fdw is any guide)
they'd prefer to consider only base relations within the join.
To support both requirements, redefine ForeignScan.fs_relids as
base+OJ relids, and add a new field fs_base_relids that's set up by
the core planner.
Large though it is, this commit just does the minimum necessary to
install the new mechanisms and get check-world passing again.
Follow-up patches will perform some cleanup. (The README additions
and comments mention some stuff that will appear in the follow-up.)
Patch by me; thanks to Richard Guo for review.
Discussion: https://postgr.es/m/830269.1656693747@sss.pgh.pa.us
2023-01-30 13:16:20 -05:00
|
|
|
create temp table t1(f1 int, f2 int);
|
|
|
|
|
create temp table t2(f1 bigint, f2 oid);
|
2020-01-01 19:31:41 -05:00
|
|
|
|
|
|
|
|
select f1 from t1 left join t2 using (f1) group by f1;
|
|
|
|
|
select f1 from t1 left join t2 using (f1) group by t1.f1;
|
|
|
|
|
select t1.f1 from t1 left join t2 using (f1) group by t1.f1;
|
|
|
|
|
-- only this one should fail:
|
|
|
|
|
select t1.f1 from t1 left join t2 using (f1) group by f1;
|
|
|
|
|
|
Make Vars be outer-join-aware.
Traditionally we used the same Var struct to represent the value
of a table column everywhere in parse and plan trees. This choice
predates our support for SQL outer joins, and it's really a pretty
bad idea with outer joins, because the Var's value can depend on
where it is in the tree: it might go to NULL above an outer join.
So expression nodes that are equal() per equalfuncs.c might not
represent the same value, which is a huge correctness hazard for
the planner.
To improve this, decorate Var nodes with a bitmapset showing
which outer joins (identified by RTE indexes) may have nulled
them at the point in the parse tree where the Var appears.
This allows us to trust that equal() Vars represent the same value.
A certain amount of klugery is still needed to cope with cases
where we re-order two outer joins, but it's possible to make it
work without sacrificing that core principle. PlaceHolderVars
receive similar decoration for the same reason.
In the planner, we include these outer join bitmapsets into the relids
that an expression is considered to depend on, and in consequence also
add outer-join relids to the relids of join RelOptInfos. This allows
us to correctly perceive whether an expression can be calculated above
or below a particular outer join.
This change affects FDWs that want to plan foreign joins. They *must*
follow suit when labeling foreign joins in order to match with the
core planner, but for many purposes (if postgres_fdw is any guide)
they'd prefer to consider only base relations within the join.
To support both requirements, redefine ForeignScan.fs_relids as
base+OJ relids, and add a new field fs_base_relids that's set up by
the core planner.
Large though it is, this commit just does the minimum necessary to
install the new mechanisms and get check-world passing again.
Follow-up patches will perform some cleanup. (The README additions
and comments mention some stuff that will appear in the follow-up.)
Patch by me; thanks to Richard Guo for review.
Discussion: https://postgr.es/m/830269.1656693747@sss.pgh.pa.us
2023-01-30 13:16:20 -05:00
|
|
|
-- check case where we have to inject nullingrels into coerced join alias
|
|
|
|
|
select f1, count(*) from
|
|
|
|
|
t1 x(x0,x1) left join (t1 left join t2 using(f1)) on (x0 = 0)
|
|
|
|
|
group by f1;
|
|
|
|
|
|
|
|
|
|
-- same, for a RelabelType coercion
|
|
|
|
|
select f2, count(*) from
|
|
|
|
|
t1 x(x0,x1) left join (t1 left join t2 using(f2)) on (x0 = 0)
|
|
|
|
|
group by f2;
|
|
|
|
|
|
2026-02-27 12:54:02 -05:00
|
|
|
-- check that we preserve join alias in GROUP BY expressions
|
|
|
|
|
create temp view v1 as
|
|
|
|
|
select f1::int from t1 left join t2 using (f1) group by f1;
|
|
|
|
|
select pg_get_viewdef('v1'::regclass);
|
|
|
|
|
|
|
|
|
|
drop view v1;
|
2020-01-01 19:31:41 -05:00
|
|
|
drop table t1, t2;
|
|
|
|
|
|
Improve performance of ORDER BY / DISTINCT aggregates
ORDER BY / DISTINCT aggreagtes have, since implemented in Postgres, been
executed by always performing a sort in nodeAgg.c to sort the tuples in
the current group into the correct order before calling the transition
function on the sorted tuples. This was not great as often there might be
an index that could have provided pre-sorted input and allowed the
transition functions to be called as the rows come in, rather than having
to store them in a tuplestore in order to sort them once all the tuples
for the group have arrived.
Here we change the planner so it requests a path with a sort order which
supports the most amount of ORDER BY / DISTINCT aggregate functions and
add new code to the executor to allow it to support the processing of
ORDER BY / DISTINCT aggregates where the tuples are already sorted in the
correct order.
Since there can be many ORDER BY / DISTINCT aggregates in any given query
level, it's very possible that we can't find an order that suits all of
these aggregates. The sort order that the planner chooses is simply the
one that suits the most aggregate functions. We take the most strictly
sorted variation of each order and see how many aggregate functions can
use that, then we try again with the order of the remaining aggregates to
see if another order would suit more aggregate functions. For example:
SELECT agg(a ORDER BY a),agg2(a ORDER BY a,b) ...
would request the sort order to be {a, b} because {a} is a subset of the
sort order of {a,b}, but;
SELECT agg(a ORDER BY a),agg2(a ORDER BY c) ...
would just pick a plan ordered by {a} (we give precedence to aggregates
which are earlier in the targetlist).
SELECT agg(a ORDER BY a),agg2(a ORDER BY b),agg3(a ORDER BY b) ...
would choose to order by {b} since two aggregates suit that vs just one
that requires input ordered by {a}.
Author: David Rowley
Reviewed-by: Ronan Dunklau, James Coleman, Ranier Vilela, Richard Guo, Tom Lane
Discussion: https://postgr.es/m/CAApHDvpHzfo92%3DR4W0%2BxVua3BUYCKMckWAmo-2t_KiXN-wYH%3Dw%40mail.gmail.com
2022-08-02 07:11:45 -04:00
|
|
|
--
|
|
|
|
|
-- Test planner's selection of pathkeys for ORDER BY aggregates
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
-- Ensure we order by four. This suits the most aggregate functions.
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select sum(two order by two),max(four order by four), min(four order by four)
|
|
|
|
|
from tenk1;
|
|
|
|
|
|
|
|
|
|
-- Ensure we order by two. It's a tie between ordering by two and four but
|
|
|
|
|
-- we tiebreak on the aggregate's position.
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select
|
|
|
|
|
sum(two order by two), max(four order by four),
|
|
|
|
|
min(four order by four), max(two order by two)
|
|
|
|
|
from tenk1;
|
|
|
|
|
|
|
|
|
|
-- Similar to above, but tiebreak on ordering by four
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select
|
|
|
|
|
max(four order by four), sum(two order by two),
|
|
|
|
|
min(four order by four), max(two order by two)
|
|
|
|
|
from tenk1;
|
|
|
|
|
|
|
|
|
|
-- Ensure this one orders by ten since there are 3 aggregates that require ten
|
|
|
|
|
-- vs two that suit two and four.
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select
|
|
|
|
|
max(four order by four), sum(two order by two),
|
|
|
|
|
min(four order by four), max(two order by two),
|
|
|
|
|
sum(ten order by ten), min(ten order by ten), max(ten order by ten)
|
|
|
|
|
from tenk1;
|
|
|
|
|
|
|
|
|
|
-- Try a case involving a GROUP BY clause where the GROUP BY column is also
|
|
|
|
|
-- part of an aggregate's ORDER BY clause. We want a sort order that works
|
|
|
|
|
-- for the GROUP BY along with the first and the last aggregate.
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select
|
|
|
|
|
sum(unique1 order by ten, two), sum(unique1 order by four),
|
|
|
|
|
sum(unique1 order by two, four)
|
|
|
|
|
from tenk1
|
|
|
|
|
group by ten;
|
|
|
|
|
|
2023-01-16 22:37:06 -05:00
|
|
|
-- Ensure that we never choose to provide presorted input to an Aggref with
|
|
|
|
|
-- a volatile function in the ORDER BY / DISTINCT clause. We want to ensure
|
|
|
|
|
-- these sorts are performed individually rather than at the query level.
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select
|
|
|
|
|
sum(unique1 order by two), sum(unique1 order by four),
|
|
|
|
|
sum(unique1 order by four, two), sum(unique1 order by two, random()),
|
|
|
|
|
sum(unique1 order by two, random(), random() + 1)
|
|
|
|
|
from tenk1
|
|
|
|
|
group by ten;
|
|
|
|
|
|
2023-02-13 02:38:37 -05:00
|
|
|
-- Ensure consecutive NULLs are properly treated as distinct from each other
|
|
|
|
|
select array_agg(distinct val)
|
|
|
|
|
from (select null as val from generate_series(1, 2));
|
|
|
|
|
|
2022-12-20 04:28:58 -05:00
|
|
|
-- Ensure no ordering is requested when enable_presorted_aggregate is off
|
|
|
|
|
set enable_presorted_aggregate to off;
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select sum(two order by two) from tenk1;
|
|
|
|
|
reset enable_presorted_aggregate;
|
|
|
|
|
|
2025-04-20 06:12:07 -04:00
|
|
|
--
|
|
|
|
|
-- Test cases with FILTER clause
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
-- Ensure we presort when the aggregate contains plain Vars
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select sum(two order by two) filter (where two > 1) from tenk1;
|
|
|
|
|
|
|
|
|
|
-- Ensure we presort for RelabelType'd Vars
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select string_agg(distinct f1, ',') filter (where length(f1) > 1)
|
|
|
|
|
from varchar_tbl;
|
|
|
|
|
|
|
|
|
|
-- Ensure we don't presort when the aggregate's argument contains an
|
|
|
|
|
-- explicit cast.
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select string_agg(distinct f1::varchar(2), ',') filter (where length(f1) > 1)
|
|
|
|
|
from varchar_tbl;
|
|
|
|
|
|
2009-12-15 12:57:48 -05:00
|
|
|
--
|
|
|
|
|
-- Test combinations of DISTINCT and/or ORDER BY
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
select array_agg(a order by b)
|
|
|
|
|
from (values (1,4),(2,3),(3,1),(4,2)) v(a,b);
|
|
|
|
|
select array_agg(a order by a)
|
|
|
|
|
from (values (1,4),(2,3),(3,1),(4,2)) v(a,b);
|
|
|
|
|
select array_agg(a order by a desc)
|
|
|
|
|
from (values (1,4),(2,3),(3,1),(4,2)) v(a,b);
|
|
|
|
|
select array_agg(b order by a desc)
|
|
|
|
|
from (values (1,4),(2,3),(3,1),(4,2)) v(a,b);
|
|
|
|
|
|
|
|
|
|
select array_agg(distinct a)
|
|
|
|
|
from (values (1),(2),(1),(3),(null),(2)) v(a);
|
|
|
|
|
select array_agg(distinct a order by a)
|
|
|
|
|
from (values (1),(2),(1),(3),(null),(2)) v(a);
|
|
|
|
|
select array_agg(distinct a order by a desc)
|
|
|
|
|
from (values (1),(2),(1),(3),(null),(2)) v(a);
|
|
|
|
|
select array_agg(distinct a order by a desc nulls last)
|
|
|
|
|
from (values (1),(2),(1),(3),(null),(2)) v(a);
|
|
|
|
|
|
|
|
|
|
-- multi-arg aggs, strict/nonstrict, distinct/order by
|
|
|
|
|
|
|
|
|
|
select aggfstr(a,b,c)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c);
|
|
|
|
|
select aggfns(a,b,c)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c);
|
|
|
|
|
|
|
|
|
|
select aggfstr(distinct a,b,c)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,3) i;
|
|
|
|
|
select aggfns(distinct a,b,c)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,3) i;
|
|
|
|
|
|
|
|
|
|
select aggfstr(distinct a,b,c order by b)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,3) i;
|
|
|
|
|
select aggfns(distinct a,b,c order by b)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,3) i;
|
|
|
|
|
|
|
|
|
|
-- test specific code paths
|
|
|
|
|
|
|
|
|
|
select aggfns(distinct a,a,c order by c using ~<~,a)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,2) i;
|
|
|
|
|
select aggfns(distinct a,a,c order by c using ~<~)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,2) i;
|
|
|
|
|
select aggfns(distinct a,a,c order by a)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,2) i;
|
|
|
|
|
select aggfns(distinct a,b,c order by a,c using ~<~,b)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,2) i;
|
|
|
|
|
|
2024-01-04 02:38:25 -05:00
|
|
|
-- test a more complex permutation that has previous caused issues
|
|
|
|
|
select
|
|
|
|
|
string_agg(distinct 'a', ','),
|
|
|
|
|
sum((
|
|
|
|
|
select sum(1)
|
|
|
|
|
from (values(1)) b(id)
|
|
|
|
|
where a.id = b.id
|
|
|
|
|
)) from unnest(array[1]) a(id);
|
|
|
|
|
|
2009-12-15 12:57:48 -05:00
|
|
|
-- check node I/O via view creation and usage, also deparsing logic
|
|
|
|
|
|
|
|
|
|
create view agg_view1 as
|
|
|
|
|
select aggfns(a,b,c)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c);
|
|
|
|
|
|
|
|
|
|
select * from agg_view1;
|
|
|
|
|
select pg_get_viewdef('agg_view1'::regclass);
|
|
|
|
|
|
|
|
|
|
create or replace view agg_view1 as
|
|
|
|
|
select aggfns(distinct a,b,c)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,3) i;
|
|
|
|
|
|
|
|
|
|
select * from agg_view1;
|
|
|
|
|
select pg_get_viewdef('agg_view1'::regclass);
|
|
|
|
|
|
|
|
|
|
create or replace view agg_view1 as
|
|
|
|
|
select aggfns(distinct a,b,c order by b)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,3) i;
|
|
|
|
|
|
|
|
|
|
select * from agg_view1;
|
|
|
|
|
select pg_get_viewdef('agg_view1'::regclass);
|
|
|
|
|
|
|
|
|
|
create or replace view agg_view1 as
|
|
|
|
|
select aggfns(a,b,c order by b+1)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c);
|
|
|
|
|
|
|
|
|
|
select * from agg_view1;
|
|
|
|
|
select pg_get_viewdef('agg_view1'::regclass);
|
|
|
|
|
|
|
|
|
|
create or replace view agg_view1 as
|
|
|
|
|
select aggfns(a,a,c order by b)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c);
|
|
|
|
|
|
|
|
|
|
select * from agg_view1;
|
|
|
|
|
select pg_get_viewdef('agg_view1'::regclass);
|
|
|
|
|
|
|
|
|
|
create or replace view agg_view1 as
|
|
|
|
|
select aggfns(a,b,c order by c using ~<~)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c);
|
|
|
|
|
|
|
|
|
|
select * from agg_view1;
|
|
|
|
|
select pg_get_viewdef('agg_view1'::regclass);
|
|
|
|
|
|
|
|
|
|
create or replace view agg_view1 as
|
|
|
|
|
select aggfns(distinct a,b,c order by a,c using ~<~,b)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,2) i;
|
|
|
|
|
|
|
|
|
|
select * from agg_view1;
|
|
|
|
|
select pg_get_viewdef('agg_view1'::regclass);
|
|
|
|
|
|
|
|
|
|
drop view agg_view1;
|
|
|
|
|
|
|
|
|
|
-- incorrect DISTINCT usage errors
|
|
|
|
|
|
|
|
|
|
select aggfns(distinct a,b,c order by i)
|
|
|
|
|
from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i;
|
|
|
|
|
select aggfns(distinct a,b,c order by a,b+1)
|
|
|
|
|
from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i;
|
|
|
|
|
select aggfns(distinct a,b,c order by a,b,i,c)
|
|
|
|
|
from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i;
|
|
|
|
|
select aggfns(distinct a,a,c order by a,b)
|
|
|
|
|
from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i;
|
2010-01-31 22:14:45 -05:00
|
|
|
|
|
|
|
|
-- string_agg tests
|
|
|
|
|
select string_agg(a,',') from (values('aaaa'),('bbbb'),('cccc')) g(a);
|
|
|
|
|
select string_agg(a,',') from (values('aaaa'),(null),('bbbb'),('cccc')) g(a);
|
2010-08-05 14:21:19 -04:00
|
|
|
select string_agg(a,'AB') from (values(null),(null),('bbbb'),('cccc')) g(a);
|
2010-01-31 22:14:45 -05:00
|
|
|
select string_agg(a,',') from (values(null),(null)) g(a);
|
2010-07-18 15:37:49 -04:00
|
|
|
|
|
|
|
|
-- check some implicit casting cases, as per bug #5564
|
2010-08-05 14:21:19 -04:00
|
|
|
select string_agg(distinct f1, ',' order by f1) from varchar_tbl; -- ok
|
|
|
|
|
select string_agg(distinct f1::text, ',' order by f1) from varchar_tbl; -- not ok
|
|
|
|
|
select string_agg(distinct f1, ',' order by f1::text) from varchar_tbl; -- not ok
|
|
|
|
|
select string_agg(distinct f1::text, ',' order by f1::text) from varchar_tbl; -- ok
|
2011-12-23 08:40:25 -05:00
|
|
|
|
2024-10-08 13:52:14 -04:00
|
|
|
-- string_agg, min, max bytea tests
|
2011-12-23 08:40:25 -05:00
|
|
|
create table bytea_test_table(v bytea);
|
|
|
|
|
|
2012-04-13 14:36:59 -04:00
|
|
|
select string_agg(v, '') from bytea_test_table;
|
2011-12-23 08:40:25 -05:00
|
|
|
|
|
|
|
|
insert into bytea_test_table values(decode('ff','hex'));
|
|
|
|
|
|
2012-04-13 14:36:59 -04:00
|
|
|
select string_agg(v, '') from bytea_test_table;
|
2011-12-23 08:40:25 -05:00
|
|
|
|
|
|
|
|
insert into bytea_test_table values(decode('aa','hex'));
|
|
|
|
|
|
2012-04-13 14:36:59 -04:00
|
|
|
select string_agg(v, '') from bytea_test_table;
|
|
|
|
|
select string_agg(v, NULL) from bytea_test_table;
|
|
|
|
|
select string_agg(v, decode('ee', 'hex')) from bytea_test_table;
|
2011-12-23 08:40:25 -05:00
|
|
|
|
2024-10-08 13:52:14 -04:00
|
|
|
select min(v) from bytea_test_table;
|
|
|
|
|
select max(v) from bytea_test_table;
|
|
|
|
|
|
|
|
|
|
insert into bytea_test_table values(decode('ffff','hex'));
|
|
|
|
|
insert into bytea_test_table values(decode('aaaa','hex'));
|
|
|
|
|
|
|
|
|
|
select min(v) from bytea_test_table;
|
|
|
|
|
select max(v) from bytea_test_table;
|
|
|
|
|
|
2011-12-23 08:40:25 -05:00
|
|
|
drop table bytea_test_table;
|
2013-07-16 20:15:36 -04:00
|
|
|
|
2023-01-22 23:35:01 -05:00
|
|
|
-- Test parallel string_agg and array_agg
|
2024-03-27 07:13:48 -04:00
|
|
|
create table pagg_test (x int, y int) with (autovacuum_enabled = off);
|
2023-01-22 23:35:01 -05:00
|
|
|
insert into pagg_test
|
|
|
|
|
select (case x % 4 when 1 then null else x end), x % 10
|
|
|
|
|
from generate_series(1,5000) x;
|
|
|
|
|
|
|
|
|
|
set parallel_setup_cost TO 0;
|
|
|
|
|
set parallel_tuple_cost TO 0;
|
|
|
|
|
set parallel_leader_participation TO 0;
|
|
|
|
|
set min_parallel_table_scan_size = 0;
|
|
|
|
|
set bytea_output = 'escape';
|
2023-01-23 03:31:46 -05:00
|
|
|
set max_parallel_workers_per_gather = 2;
|
2023-01-22 23:35:01 -05:00
|
|
|
|
|
|
|
|
-- create a view as we otherwise have to repeat this query a few times.
|
|
|
|
|
create view v_pagg_test AS
|
|
|
|
|
select
|
|
|
|
|
y,
|
|
|
|
|
min(t) AS tmin,max(t) AS tmax,count(distinct t) AS tndistinct,
|
|
|
|
|
min(b) AS bmin,max(b) AS bmax,count(distinct b) AS bndistinct,
|
|
|
|
|
min(a) AS amin,max(a) AS amax,count(distinct a) AS andistinct,
|
|
|
|
|
min(aa) AS aamin,max(aa) AS aamax,count(distinct aa) AS aandistinct
|
|
|
|
|
from (
|
|
|
|
|
select
|
|
|
|
|
y,
|
|
|
|
|
unnest(regexp_split_to_array(a1.t, ','))::int AS t,
|
|
|
|
|
unnest(regexp_split_to_array(a1.b::text, ',')) AS b,
|
|
|
|
|
unnest(a1.a) AS a,
|
|
|
|
|
unnest(a1.aa) AS aa
|
|
|
|
|
from (
|
|
|
|
|
select
|
|
|
|
|
y,
|
|
|
|
|
string_agg(x::text, ',') AS t,
|
|
|
|
|
string_agg(x::text::bytea, ',') AS b,
|
|
|
|
|
array_agg(x) AS a,
|
|
|
|
|
array_agg(ARRAY[x]) AS aa
|
|
|
|
|
from pagg_test
|
|
|
|
|
group by y
|
|
|
|
|
) a1
|
|
|
|
|
) a2
|
|
|
|
|
group by y;
|
|
|
|
|
|
|
|
|
|
-- Ensure results are correct.
|
|
|
|
|
select * from v_pagg_test order by y;
|
|
|
|
|
|
|
|
|
|
-- Ensure parallel aggregation is actually being used.
|
|
|
|
|
explain (costs off) select * from v_pagg_test order by y;
|
|
|
|
|
|
|
|
|
|
-- Ensure results are the same without parallel aggregation.
|
2025-03-09 13:11:20 -04:00
|
|
|
set max_parallel_workers_per_gather = 0;
|
2023-01-22 23:35:01 -05:00
|
|
|
select * from v_pagg_test order by y;
|
|
|
|
|
|
2025-03-09 13:11:20 -04:00
|
|
|
-- Check that we don't fail on anonymous record types.
|
|
|
|
|
set max_parallel_workers_per_gather = 2;
|
|
|
|
|
explain (costs off)
|
|
|
|
|
select array_dims(array_agg(s)) from (select * from pagg_test) s;
|
|
|
|
|
select array_dims(array_agg(s)) from (select * from pagg_test) s;
|
|
|
|
|
|
2023-01-22 23:35:01 -05:00
|
|
|
-- Clean up
|
|
|
|
|
reset max_parallel_workers_per_gather;
|
|
|
|
|
reset bytea_output;
|
|
|
|
|
reset min_parallel_table_scan_size;
|
|
|
|
|
reset parallel_leader_participation;
|
|
|
|
|
reset parallel_tuple_cost;
|
|
|
|
|
reset parallel_setup_cost;
|
|
|
|
|
|
|
|
|
|
drop view v_pagg_test;
|
|
|
|
|
drop table pagg_test;
|
|
|
|
|
|
2013-07-16 20:15:36 -04:00
|
|
|
-- FILTER tests
|
|
|
|
|
|
|
|
|
|
select min(unique1) filter (where unique1 > 100) from tenk1;
|
|
|
|
|
|
2017-10-16 15:24:36 -04:00
|
|
|
select sum(1/ten) filter (where ten > 0) from tenk1;
|
|
|
|
|
|
2013-07-16 20:15:36 -04:00
|
|
|
select ten, sum(distinct four) filter (where four::text ~ '123') from onek a
|
|
|
|
|
group by ten;
|
|
|
|
|
|
|
|
|
|
select ten, sum(distinct four) filter (where four > 10) from onek a
|
|
|
|
|
group by ten
|
|
|
|
|
having exists (select 1 from onek b where sum(distinct a.four) = b.four);
|
|
|
|
|
|
|
|
|
|
select max(foo COLLATE "C") filter (where (bar collate "POSIX") > '0')
|
|
|
|
|
from (values ('a', 'b')) AS v(foo,bar);
|
|
|
|
|
|
2023-02-22 03:32:12 -05:00
|
|
|
select any_value(v) filter (where v > 2) from (values (1), (2), (3)) as v (v);
|
|
|
|
|
|
2013-07-16 20:15:36 -04:00
|
|
|
-- outer reference in FILTER (PostgreSQL extension)
|
|
|
|
|
select (select count(*)
|
|
|
|
|
from (values (1)) t0(inner_c))
|
|
|
|
|
from (values (2),(3)) t1(outer_c); -- inner query is aggregation query
|
|
|
|
|
select (select count(*) filter (where outer_c <> 0)
|
|
|
|
|
from (values (1)) t0(inner_c))
|
|
|
|
|
from (values (2),(3)) t1(outer_c); -- outer query is aggregation query
|
|
|
|
|
select (select count(inner_c) filter (where outer_c <> 0)
|
|
|
|
|
from (values (1)) t0(inner_c))
|
|
|
|
|
from (values (2),(3)) t1(outer_c); -- inner query is aggregation query
|
|
|
|
|
select
|
|
|
|
|
(select max((select i.unique2 from tenk1 i where i.unique1 = o.unique1))
|
|
|
|
|
filter (where o.unique1 < 10))
|
|
|
|
|
from tenk1 o; -- outer query is aggregation query
|
|
|
|
|
|
|
|
|
|
-- subquery in FILTER clause (PostgreSQL extension)
|
|
|
|
|
select sum(unique1) FILTER (WHERE
|
|
|
|
|
unique1 IN (SELECT unique1 FROM onek where unique1 < 100)) FROM tenk1;
|
|
|
|
|
|
|
|
|
|
-- exercise lots of aggregate parts with FILTER
|
|
|
|
|
select aggfns(distinct a,b,c order by a,c using ~<~,b) filter (where a > 1)
|
|
|
|
|
from (values (1,3,'foo'),(0,null,null),(2,2,'bar'),(3,1,'baz')) v(a,b,c),
|
|
|
|
|
generate_series(1,2) i;
|
Allow aggregate functions to be VARIADIC.
There's no inherent reason why an aggregate function can't be variadic
(even VARIADIC ANY) if its transition function can handle the case.
Indeed, this patch to add the feature touches none of the planner or
executor, and little of the parser; the main missing stuff was DDL and
pg_dump support.
It is true that variadic aggregates can create the same sort of ambiguity
about parameters versus ORDER BY keys that was complained of when we
(briefly) had both one- and two-argument forms of string_agg(). However,
the policy formed in response to that discussion only said that we'd not
create any built-in aggregates with varying numbers of arguments, not that
we shouldn't allow users to do it. So the logical extension of that is
we can allow users to make variadic aggregates as long as we're wary about
shipping any such in core.
In passing, this patch allows aggregate function arguments to be named, to
the extent of remembering the names in pg_proc and dumping them in pg_dump.
You can't yet call an aggregate using named-parameter notation. That seems
like a likely future extension, but it'll take some work, and it's not what
this patch is really about. Likewise, there's still some work needed to
make window functions handle VARIADIC fully, but I left that for another
day.
initdb forced because of new aggvariadic field in Aggref parse nodes.
2013-09-03 17:08:38 -04:00
|
|
|
|
Fix check_agg_arguments' examination of aggregate FILTER clauses.
Recursion into the FILTER clause was mis-implemented, such that a
relevant Var or Aggref at the very top of the FILTER clause would
be ignored. (Of course, that'd have to be a plain boolean Var or
boolean-returning aggregate.) The consequence would be
mis-identification of the correct semantic level of the aggregate,
which could lead to not-per-spec query behavior. If the FILTER
expression is an aggregate, this could also lead to failure to issue
an expected "aggregate function calls cannot be nested" error, which
would likely result in a core dump later on, since the planner and
executor aren't expecting such cases to appear.
The root cause is that commit b560ec1b0 blindly copied some code
that assumed it's recursing into a List, and thus didn't examine the
top-level node. To forestall questions about why this call doesn't
look like the others, as well as possible future copy-and-paste
mistakes, let's change all three check_agg_arguments_walker calls in
check_agg_arguments, even though only the one for the filter clause
is really broken.
Per bug #17152 from Zhiyong Wu. This has been wrong since we
implemented FILTER, so back-patch to all supported versions.
(Testing suggests that pre-v11 branches manage to avoid crashing
in the bad-Aggref case, thanks to "redundant" checks in ExecInitAgg.
But I'm not sure how thorough that protection is, and anyway the
wrong-behavior issue remains, so fix 9.6 and 10 too.)
Discussion: https://postgr.es/m/17152-c7f906cc1a88e61b@postgresql.org
2021-08-18 18:12:51 -04:00
|
|
|
-- check handling of bare boolean Var in FILTER
|
|
|
|
|
select max(0) filter (where b1) from bool_test;
|
|
|
|
|
select (select max(0) filter (where b1)) from bool_test;
|
|
|
|
|
|
|
|
|
|
-- check for correct detection of nested-aggregate errors in FILTER
|
|
|
|
|
select max(unique1) filter (where sum(ten) > 0) from tenk1;
|
|
|
|
|
select (select max(unique1) filter (where sum(ten) > 0) from int8_tbl) from tenk1;
|
|
|
|
|
select max(unique1) filter (where bool_or(ten > 0)) from tenk1;
|
|
|
|
|
select (select max(unique1) filter (where bool_or(ten > 0)) from int8_tbl) from tenk1;
|
|
|
|
|
|
|
|
|
|
|
Support ordered-set (WITHIN GROUP) aggregates.
This patch introduces generic support for ordered-set and hypothetical-set
aggregate functions, as well as implementations of the instances defined in
SQL:2008 (percentile_cont(), percentile_disc(), rank(), dense_rank(),
percent_rank(), cume_dist()). We also added mode() though it is not in the
spec, as well as versions of percentile_cont() and percentile_disc() that
can compute multiple percentile values in one pass over the data.
Unlike the original submission, this patch puts full control of the sorting
process in the hands of the aggregate's support functions. To allow the
support functions to find out how they're supposed to sort, a new API
function AggGetAggref() is added to nodeAgg.c. This allows retrieval of
the aggregate call's Aggref node, which may have other uses beyond the
immediate need. There is also support for ordered-set aggregates to
install cleanup callback functions, so that they can be sure that
infrastructure such as tuplesort objects gets cleaned up.
In passing, make some fixes in the recently-added support for variadic
aggregates, and make some editorial adjustments in the recent FILTER
additions for aggregates. Also, simplify use of IsBinaryCoercible() by
allowing it to succeed whenever the target type is ANY or ANYELEMENT.
It was inconsistent that it dealt with other polymorphic target types
but not these.
Atri Sharma and Andrew Gierth; reviewed by Pavel Stehule and Vik Fearing,
and rather heavily editorialized upon by Tom Lane
2013-12-23 16:11:35 -05:00
|
|
|
-- ordered-set aggregates
|
|
|
|
|
|
|
|
|
|
select p, percentile_cont(p) within group (order by x::float8)
|
|
|
|
|
from generate_series(1,5) x,
|
|
|
|
|
(values (0::float8),(0.1),(0.25),(0.4),(0.5),(0.6),(0.75),(0.9),(1)) v(p)
|
|
|
|
|
group by p order by p;
|
|
|
|
|
|
|
|
|
|
select p, percentile_cont(p order by p) within group (order by x) -- error
|
|
|
|
|
from generate_series(1,5) x,
|
|
|
|
|
(values (0::float8),(0.1),(0.25),(0.4),(0.5),(0.6),(0.75),(0.9),(1)) v(p)
|
|
|
|
|
group by p order by p;
|
|
|
|
|
|
|
|
|
|
select p, sum() within group (order by x::float8) -- error
|
|
|
|
|
from generate_series(1,5) x,
|
|
|
|
|
(values (0::float8),(0.1),(0.25),(0.4),(0.5),(0.6),(0.75),(0.9),(1)) v(p)
|
|
|
|
|
group by p order by p;
|
|
|
|
|
|
|
|
|
|
select p, percentile_cont(p,p) -- error
|
|
|
|
|
from generate_series(1,5) x,
|
|
|
|
|
(values (0::float8),(0.1),(0.25),(0.4),(0.5),(0.6),(0.75),(0.9),(1)) v(p)
|
|
|
|
|
group by p order by p;
|
|
|
|
|
|
|
|
|
|
select percentile_cont(0.5) within group (order by b) from aggtest;
|
|
|
|
|
select percentile_cont(0.5) within group (order by b), sum(b) from aggtest;
|
|
|
|
|
select percentile_cont(0.5) within group (order by thousand) from tenk1;
|
|
|
|
|
select percentile_disc(0.5) within group (order by thousand) from tenk1;
|
|
|
|
|
select rank(3) within group (order by x)
|
|
|
|
|
from (values (1),(1),(2),(2),(3),(3),(4)) v(x);
|
|
|
|
|
select cume_dist(3) within group (order by x)
|
|
|
|
|
from (values (1),(1),(2),(2),(3),(3),(4)) v(x);
|
|
|
|
|
select percent_rank(3) within group (order by x)
|
|
|
|
|
from (values (1),(1),(2),(2),(3),(3),(4),(5)) v(x);
|
|
|
|
|
select dense_rank(3) within group (order by x)
|
|
|
|
|
from (values (1),(1),(2),(2),(3),(3),(4)) v(x);
|
|
|
|
|
|
|
|
|
|
select percentile_disc(array[0,0.1,0.25,0.5,0.75,0.9,1]) within group (order by thousand)
|
|
|
|
|
from tenk1;
|
|
|
|
|
select percentile_cont(array[0,0.25,0.5,0.75,1]) within group (order by thousand)
|
|
|
|
|
from tenk1;
|
|
|
|
|
select percentile_disc(array[[null,1,0.5],[0.75,0.25,null]]) within group (order by thousand)
|
|
|
|
|
from tenk1;
|
2014-12-13 11:49:16 -05:00
|
|
|
select percentile_cont(array[0,1,0.25,0.75,0.5,1,0.3,0.32,0.35,0.38,0.4]) within group (order by x)
|
Support ordered-set (WITHIN GROUP) aggregates.
This patch introduces generic support for ordered-set and hypothetical-set
aggregate functions, as well as implementations of the instances defined in
SQL:2008 (percentile_cont(), percentile_disc(), rank(), dense_rank(),
percent_rank(), cume_dist()). We also added mode() though it is not in the
spec, as well as versions of percentile_cont() and percentile_disc() that
can compute multiple percentile values in one pass over the data.
Unlike the original submission, this patch puts full control of the sorting
process in the hands of the aggregate's support functions. To allow the
support functions to find out how they're supposed to sort, a new API
function AggGetAggref() is added to nodeAgg.c. This allows retrieval of
the aggregate call's Aggref node, which may have other uses beyond the
immediate need. There is also support for ordered-set aggregates to
install cleanup callback functions, so that they can be sure that
infrastructure such as tuplesort objects gets cleaned up.
In passing, make some fixes in the recently-added support for variadic
aggregates, and make some editorial adjustments in the recent FILTER
additions for aggregates. Also, simplify use of IsBinaryCoercible() by
allowing it to succeed whenever the target type is ANY or ANYELEMENT.
It was inconsistent that it dealt with other polymorphic target types
but not these.
Atri Sharma and Andrew Gierth; reviewed by Pavel Stehule and Vik Fearing,
and rather heavily editorialized upon by Tom Lane
2013-12-23 16:11:35 -05:00
|
|
|
from generate_series(1,6) x;
|
|
|
|
|
|
|
|
|
|
select ten, mode() within group (order by string4) from tenk1 group by ten;
|
|
|
|
|
|
|
|
|
|
select percentile_disc(array[0.25,0.5,0.75]) within group (order by x)
|
|
|
|
|
from unnest('{fred,jim,fred,jack,jill,fred,jill,jim,jim,sheila,jim,sheila}'::text[]) u(x);
|
|
|
|
|
|
|
|
|
|
-- check collation propagates up in suitable cases:
|
|
|
|
|
select pg_collation_for(percentile_disc(1) within group (order by x collate "POSIX"))
|
|
|
|
|
from (values ('fred'),('jim')) v(x);
|
|
|
|
|
|
|
|
|
|
-- ordered-set aggs created with CREATE AGGREGATE
|
|
|
|
|
select test_rank(3) within group (order by x)
|
|
|
|
|
from (values (1),(1),(2),(2),(3),(3),(4)) v(x);
|
|
|
|
|
select test_percentile_disc(0.5) within group (order by thousand) from tenk1;
|
|
|
|
|
|
|
|
|
|
-- ordered-set aggs can't use ungrouped vars in direct args:
|
|
|
|
|
select rank(x) within group (order by x) from generate_series(1,5) x;
|
|
|
|
|
|
|
|
|
|
-- outer-level agg can't use a grouped arg of a lower level, either:
|
|
|
|
|
select array(select percentile_disc(a) within group (order by x)
|
|
|
|
|
from (values (0.3),(0.7)) v(a) group by a)
|
|
|
|
|
from generate_series(1,5) g(x);
|
|
|
|
|
|
|
|
|
|
-- agg in the direct args is a grouping violation, too:
|
|
|
|
|
select rank(sum(x)) within group (order by x) from generate_series(1,5) x;
|
|
|
|
|
|
|
|
|
|
-- hypothetical-set type unification and argument-count failures:
|
|
|
|
|
select rank(3) within group (order by x) from (values ('fred'),('jim')) v(x);
|
|
|
|
|
select rank(3) within group (order by stringu1,stringu2) from tenk1;
|
|
|
|
|
select rank('fred') within group (order by x) from generate_series(1,5) x;
|
|
|
|
|
select rank('adam'::text collate "C") within group (order by x collate "POSIX")
|
|
|
|
|
from (values ('fred'),('jim')) v(x);
|
|
|
|
|
-- hypothetical-set type unification successes:
|
|
|
|
|
select rank('adam'::varchar) within group (order by x) from (values ('fred'),('jim')) v(x);
|
|
|
|
|
select rank('3') within group (order by x) from generate_series(1,5) x;
|
|
|
|
|
|
|
|
|
|
-- divide by zero check
|
|
|
|
|
select percent_rank(0) within group (order by x) from generate_series(1,0) x;
|
|
|
|
|
|
|
|
|
|
-- deparse and multiple features:
|
|
|
|
|
create view aggordview1 as
|
|
|
|
|
select ten,
|
|
|
|
|
percentile_disc(0.5) within group (order by thousand) as p50,
|
|
|
|
|
percentile_disc(0.5) within group (order by thousand) filter (where hundred=1) as px,
|
|
|
|
|
rank(5,'AZZZZ',50) within group (order by hundred, string4 desc, hundred)
|
|
|
|
|
from tenk1
|
|
|
|
|
group by ten order by ten;
|
|
|
|
|
|
|
|
|
|
select pg_get_viewdef('aggordview1');
|
|
|
|
|
select * from aggordview1 order by ten;
|
|
|
|
|
drop view aggordview1;
|
|
|
|
|
|
Allow aggregate functions to be VARIADIC.
There's no inherent reason why an aggregate function can't be variadic
(even VARIADIC ANY) if its transition function can handle the case.
Indeed, this patch to add the feature touches none of the planner or
executor, and little of the parser; the main missing stuff was DDL and
pg_dump support.
It is true that variadic aggregates can create the same sort of ambiguity
about parameters versus ORDER BY keys that was complained of when we
(briefly) had both one- and two-argument forms of string_agg(). However,
the policy formed in response to that discussion only said that we'd not
create any built-in aggregates with varying numbers of arguments, not that
we shouldn't allow users to do it. So the logical extension of that is
we can allow users to make variadic aggregates as long as we're wary about
shipping any such in core.
In passing, this patch allows aggregate function arguments to be named, to
the extent of remembering the names in pg_proc and dumping them in pg_dump.
You can't yet call an aggregate using named-parameter notation. That seems
like a likely future extension, but it'll take some work, and it's not what
this patch is really about. Likewise, there's still some work needed to
make window functions handle VARIADIC fully, but I left that for another
day.
initdb forced because of new aggvariadic field in Aggref parse nodes.
2013-09-03 17:08:38 -04:00
|
|
|
-- variadic aggregates
|
|
|
|
|
select least_agg(q1,q2) from int8_tbl;
|
|
|
|
|
select least_agg(variadic array[q1,q2]) from int8_tbl;
|
2015-08-04 10:53:10 -04:00
|
|
|
|
Introduce "anycompatible" family of polymorphic types.
This patch adds the pseudo-types anycompatible, anycompatiblearray,
anycompatiblenonarray, and anycompatiblerange. They work much like
anyelement, anyarray, anynonarray, and anyrange respectively, except
that the actual input values need not match precisely in type.
Instead, if we can find a common supertype (using the same rules
as for UNION/CASE type resolution), then the parser automatically
promotes the input values to that type. For example,
"myfunc(anycompatible, anycompatible)" can match a call with one
integer and one bigint argument, with the integer automatically
promoted to bigint. With anyelement in the definition, the user
would have had to cast the integer explicitly.
The new types also provide a second, independent set of type variables
for function matching; thus with "myfunc(anyelement, anyelement,
anycompatible) returns anycompatible" the first two arguments are
constrained to be the same type, but the third can be some other
type, and the result has the type of the third argument. The need
for more than one set of type variables was foreseen back when we
first invented the polymorphic types, but we never did anything
about it.
Pavel Stehule, revised a bit by me
Discussion: https://postgr.es/m/CAFj8pRDna7VqNi8gR+Tt2Ktmz0cq5G93guc3Sbn_NVPLdXAkqA@mail.gmail.com
2020-03-19 11:43:11 -04:00
|
|
|
select cleast_agg(q1,q2) from int8_tbl;
|
|
|
|
|
select cleast_agg(4.5,f1) from int4_tbl;
|
|
|
|
|
select cleast_agg(variadic array[4.5,f1]) from int4_tbl;
|
|
|
|
|
select pg_typeof(cleast_agg(variadic array[4.5,f1])) from int4_tbl;
|
2015-08-04 10:53:10 -04:00
|
|
|
|
|
|
|
|
-- test aggregates with common transition functions share the same states
|
|
|
|
|
begin work;
|
|
|
|
|
|
|
|
|
|
create type avg_state as (total bigint, count bigint);
|
|
|
|
|
|
|
|
|
|
create or replace function avg_transfn(state avg_state, n int) returns avg_state as
|
|
|
|
|
$$
|
|
|
|
|
declare new_state avg_state;
|
|
|
|
|
begin
|
|
|
|
|
raise notice 'avg_transfn called with %', n;
|
|
|
|
|
if state is null then
|
|
|
|
|
if n is not null then
|
|
|
|
|
new_state.total := n;
|
|
|
|
|
new_state.count := 1;
|
|
|
|
|
return new_state;
|
|
|
|
|
end if;
|
|
|
|
|
return null;
|
|
|
|
|
elsif n is not null then
|
|
|
|
|
state.total := state.total + n;
|
|
|
|
|
state.count := state.count + 1;
|
|
|
|
|
return state;
|
|
|
|
|
end if;
|
|
|
|
|
|
|
|
|
|
return null;
|
|
|
|
|
end
|
|
|
|
|
$$ language plpgsql;
|
|
|
|
|
|
|
|
|
|
create function avg_finalfn(state avg_state) returns int4 as
|
|
|
|
|
$$
|
|
|
|
|
begin
|
|
|
|
|
if state is null then
|
|
|
|
|
return NULL;
|
|
|
|
|
else
|
|
|
|
|
return state.total / state.count;
|
|
|
|
|
end if;
|
|
|
|
|
end
|
|
|
|
|
$$ language plpgsql;
|
|
|
|
|
|
|
|
|
|
create function sum_finalfn(state avg_state) returns int4 as
|
|
|
|
|
$$
|
|
|
|
|
begin
|
|
|
|
|
if state is null then
|
|
|
|
|
return NULL;
|
|
|
|
|
else
|
|
|
|
|
return state.total;
|
|
|
|
|
end if;
|
|
|
|
|
end
|
|
|
|
|
$$ language plpgsql;
|
|
|
|
|
|
|
|
|
|
create aggregate my_avg(int4)
|
|
|
|
|
(
|
|
|
|
|
stype = avg_state,
|
|
|
|
|
sfunc = avg_transfn,
|
|
|
|
|
finalfunc = avg_finalfn
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
create aggregate my_sum(int4)
|
|
|
|
|
(
|
|
|
|
|
stype = avg_state,
|
|
|
|
|
sfunc = avg_transfn,
|
|
|
|
|
finalfunc = sum_finalfn
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
-- aggregate state should be shared as aggs are the same.
|
|
|
|
|
select my_avg(one),my_avg(one) from (values(1),(3)) t(one);
|
|
|
|
|
|
|
|
|
|
-- aggregate state should be shared as transfn is the same for both aggs.
|
|
|
|
|
select my_avg(one),my_sum(one) from (values(1),(3)) t(one);
|
|
|
|
|
|
2016-12-20 02:20:17 -05:00
|
|
|
-- same as previous one, but with DISTINCT, which requires sorting the input.
|
|
|
|
|
select my_avg(distinct one),my_sum(distinct one) from (values(1),(3),(1)) t(one);
|
|
|
|
|
|
2015-08-04 10:53:10 -04:00
|
|
|
-- shouldn't share states due to the distinctness not matching.
|
|
|
|
|
select my_avg(distinct one),my_sum(one) from (values(1),(3)) t(one);
|
|
|
|
|
|
|
|
|
|
-- shouldn't share states due to the filter clause not matching.
|
|
|
|
|
select my_avg(one) filter (where one > 1),my_sum(one) from (values(1),(3)) t(one);
|
|
|
|
|
|
|
|
|
|
-- this should not share the state due to different input columns.
|
|
|
|
|
select my_avg(one),my_sum(two) from (values(1,2),(3,4)) t(one,two);
|
|
|
|
|
|
2017-10-16 15:51:23 -04:00
|
|
|
-- exercise cases where OSAs share state
|
Prevent sharing transition states between ordered-set aggregates.
This ought to work, but the built-in OSAs are not capable of coping,
because their final-functions destructively modify their transition
state (specifically, the contained tuplesort object). That was fine
when those functions were written, but commit 804163bc2 moved the
goalposts without telling orderedsetaggs.c.
We should fix the built-in OSAs to support this, but it will take
a little work, especially if we don't want to sacrifice performance
in the normal non-shared-state case. Given that it took a year after
9.6 release for anyone to notice this bug, we should not prioritize
sharable-state over nonsharable-state performance. And a proper fix
is likely to be more complicated than we'd want to back-patch, too.
Therefore, let's just put in this stop-gap patch to prevent nodeAgg.c
from choosing to use shared state for OSAs. We can revert it in HEAD
when we get a better fix.
Report from Lukas Eder, diagnosis by me, patch by David Rowley.
Back-patch to 9.6 where the problem was introduced.
Discussion: https://postgr.es/m/CAB4ELO5RZhOamuT9Xsf72ozbenDLLXZKSk07FiSVsuJNZB861A@mail.gmail.com
2017-10-11 22:18:01 -04:00
|
|
|
select
|
|
|
|
|
percentile_cont(0.5) within group (order by a),
|
|
|
|
|
percentile_disc(0.5) within group (order by a)
|
|
|
|
|
from (values(1::float8),(3),(5),(7)) t(a);
|
|
|
|
|
|
2017-10-16 15:51:23 -04:00
|
|
|
select
|
|
|
|
|
percentile_cont(0.25) within group (order by a),
|
|
|
|
|
percentile_disc(0.5) within group (order by a)
|
|
|
|
|
from (values(1::float8),(3),(5),(7)) t(a);
|
|
|
|
|
|
|
|
|
|
-- these can't share state currently
|
Prevent sharing transition states between ordered-set aggregates.
This ought to work, but the built-in OSAs are not capable of coping,
because their final-functions destructively modify their transition
state (specifically, the contained tuplesort object). That was fine
when those functions were written, but commit 804163bc2 moved the
goalposts without telling orderedsetaggs.c.
We should fix the built-in OSAs to support this, but it will take
a little work, especially if we don't want to sacrifice performance
in the normal non-shared-state case. Given that it took a year after
9.6 release for anyone to notice this bug, we should not prioritize
sharable-state over nonsharable-state performance. And a proper fix
is likely to be more complicated than we'd want to back-patch, too.
Therefore, let's just put in this stop-gap patch to prevent nodeAgg.c
from choosing to use shared state for OSAs. We can revert it in HEAD
when we get a better fix.
Report from Lukas Eder, diagnosis by me, patch by David Rowley.
Back-patch to 9.6 where the problem was introduced.
Discussion: https://postgr.es/m/CAB4ELO5RZhOamuT9Xsf72ozbenDLLXZKSk07FiSVsuJNZB861A@mail.gmail.com
2017-10-11 22:18:01 -04:00
|
|
|
select
|
|
|
|
|
rank(4) within group (order by a),
|
|
|
|
|
dense_rank(4) within group (order by a)
|
|
|
|
|
from (values(1),(3),(5),(7)) t(a);
|
|
|
|
|
|
2015-08-04 10:53:10 -04:00
|
|
|
-- test that aggs with the same sfunc and initcond share the same agg state
|
|
|
|
|
create aggregate my_sum_init(int4)
|
|
|
|
|
(
|
|
|
|
|
stype = avg_state,
|
|
|
|
|
sfunc = avg_transfn,
|
|
|
|
|
finalfunc = sum_finalfn,
|
|
|
|
|
initcond = '(10,0)'
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
create aggregate my_avg_init(int4)
|
|
|
|
|
(
|
|
|
|
|
stype = avg_state,
|
|
|
|
|
sfunc = avg_transfn,
|
|
|
|
|
finalfunc = avg_finalfn,
|
|
|
|
|
initcond = '(10,0)'
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
create aggregate my_avg_init2(int4)
|
|
|
|
|
(
|
|
|
|
|
stype = avg_state,
|
|
|
|
|
sfunc = avg_transfn,
|
|
|
|
|
finalfunc = avg_finalfn,
|
|
|
|
|
initcond = '(4,0)'
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
-- state should be shared if INITCONDs are matching
|
|
|
|
|
select my_sum_init(one),my_avg_init(one) from (values(1),(3)) t(one);
|
|
|
|
|
|
|
|
|
|
-- Varying INITCONDs should cause the states not to be shared.
|
|
|
|
|
select my_sum_init(one),my_avg_init2(one) from (values(1),(3)) t(one);
|
|
|
|
|
|
|
|
|
|
rollback;
|
|
|
|
|
|
|
|
|
|
-- test aggregate state sharing to ensure it works if one aggregate has a
|
|
|
|
|
-- finalfn and the other one has none.
|
|
|
|
|
begin work;
|
|
|
|
|
|
|
|
|
|
create or replace function sum_transfn(state int4, n int4) returns int4 as
|
|
|
|
|
$$
|
|
|
|
|
declare new_state int4;
|
|
|
|
|
begin
|
|
|
|
|
raise notice 'sum_transfn called with %', n;
|
|
|
|
|
if state is null then
|
|
|
|
|
if n is not null then
|
|
|
|
|
new_state := n;
|
|
|
|
|
return new_state;
|
|
|
|
|
end if;
|
|
|
|
|
return null;
|
|
|
|
|
elsif n is not null then
|
|
|
|
|
state := state + n;
|
|
|
|
|
return state;
|
|
|
|
|
end if;
|
|
|
|
|
|
|
|
|
|
return null;
|
|
|
|
|
end
|
|
|
|
|
$$ language plpgsql;
|
|
|
|
|
|
|
|
|
|
create function halfsum_finalfn(state int4) returns int4 as
|
|
|
|
|
$$
|
|
|
|
|
begin
|
|
|
|
|
if state is null then
|
|
|
|
|
return NULL;
|
|
|
|
|
else
|
|
|
|
|
return state / 2;
|
|
|
|
|
end if;
|
|
|
|
|
end
|
|
|
|
|
$$ language plpgsql;
|
|
|
|
|
|
|
|
|
|
create aggregate my_sum(int4)
|
|
|
|
|
(
|
|
|
|
|
stype = int4,
|
|
|
|
|
sfunc = sum_transfn
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
create aggregate my_half_sum(int4)
|
|
|
|
|
(
|
|
|
|
|
stype = int4,
|
|
|
|
|
sfunc = sum_transfn,
|
|
|
|
|
finalfunc = halfsum_finalfn
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
-- Agg state should be shared even though my_sum has no finalfn
|
|
|
|
|
select my_sum(one),my_half_sum(one) from (values(1),(2),(3),(4)) t(one);
|
|
|
|
|
|
|
|
|
|
rollback;
|
2017-11-23 20:13:09 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
-- test that the aggregate transition logic correctly handles
|
|
|
|
|
-- transition / combine functions returning NULL
|
|
|
|
|
|
|
|
|
|
-- First test the case of a normal transition function returning NULL
|
|
|
|
|
BEGIN;
|
|
|
|
|
CREATE FUNCTION balkifnull(int8, int4)
|
|
|
|
|
RETURNS int8
|
|
|
|
|
STRICT
|
|
|
|
|
LANGUAGE plpgsql AS $$
|
|
|
|
|
BEGIN
|
|
|
|
|
IF $1 IS NULL THEN
|
|
|
|
|
RAISE 'erroneously called with NULL argument';
|
|
|
|
|
END IF;
|
|
|
|
|
RETURN NULL;
|
|
|
|
|
END$$;
|
|
|
|
|
|
Avoid unnecessary use of pg_strcasecmp for already-downcased identifiers.
We have a lot of code in which option names, which from the user's
viewpoint are logically keywords, are passed through the grammar as plain
identifiers, and then matched to string literals during command execution.
This approach avoids making words into lexer keywords unnecessarily. Some
places matched these strings using plain strcmp, some using pg_strcasecmp.
But the latter should be unnecessary since identifiers would have been
downcased on their way through the parser. Aside from any efficiency
concerns (probably not a big factor), the lack of consistency in this area
creates a hazard of subtle bugs due to different places coming to different
conclusions about whether two option names are the same or different.
Hence, standardize on using strcmp() to match any option names that are
expected to have been fed through the parser.
This does create a user-visible behavioral change, which is that while
formerly all of these would work:
alter table foo set (fillfactor = 50);
alter table foo set (FillFactor = 50);
alter table foo set ("fillfactor" = 50);
alter table foo set ("FillFactor" = 50);
now the last case will fail because that double-quoted identifier is
different from the others. However, none of our documentation says that
you can use a quoted identifier in such contexts at all, and we should
discourage doing so since it would break if we ever decide to parse such
constructs as true lexer keywords rather than poor man's substitutes.
So this shouldn't create a significant compatibility issue for users.
Daniel Gustafsson, reviewed by Michael Paquier, small changes by me
Discussion: https://postgr.es/m/29405B24-564E-476B-98C0-677A29805B84@yesql.se
2018-01-26 18:25:02 -05:00
|
|
|
CREATE AGGREGATE balk(int4)
|
|
|
|
|
(
|
2017-11-23 20:13:09 -05:00
|
|
|
SFUNC = balkifnull(int8, int4),
|
|
|
|
|
STYPE = int8,
|
Avoid unnecessary use of pg_strcasecmp for already-downcased identifiers.
We have a lot of code in which option names, which from the user's
viewpoint are logically keywords, are passed through the grammar as plain
identifiers, and then matched to string literals during command execution.
This approach avoids making words into lexer keywords unnecessarily. Some
places matched these strings using plain strcmp, some using pg_strcasecmp.
But the latter should be unnecessary since identifiers would have been
downcased on their way through the parser. Aside from any efficiency
concerns (probably not a big factor), the lack of consistency in this area
creates a hazard of subtle bugs due to different places coming to different
conclusions about whether two option names are the same or different.
Hence, standardize on using strcmp() to match any option names that are
expected to have been fed through the parser.
This does create a user-visible behavioral change, which is that while
formerly all of these would work:
alter table foo set (fillfactor = 50);
alter table foo set (FillFactor = 50);
alter table foo set ("fillfactor" = 50);
alter table foo set ("FillFactor" = 50);
now the last case will fail because that double-quoted identifier is
different from the others. However, none of our documentation says that
you can use a quoted identifier in such contexts at all, and we should
discourage doing so since it would break if we ever decide to parse such
constructs as true lexer keywords rather than poor man's substitutes.
So this shouldn't create a significant compatibility issue for users.
Daniel Gustafsson, reviewed by Michael Paquier, small changes by me
Discussion: https://postgr.es/m/29405B24-564E-476B-98C0-677A29805B84@yesql.se
2018-01-26 18:25:02 -05:00
|
|
|
PARALLEL = SAFE,
|
|
|
|
|
INITCOND = '0'
|
|
|
|
|
);
|
2017-11-23 20:13:09 -05:00
|
|
|
|
2017-11-24 00:29:20 -05:00
|
|
|
SELECT balk(hundred) FROM tenk1;
|
2017-11-23 20:13:09 -05:00
|
|
|
|
|
|
|
|
ROLLBACK;
|
|
|
|
|
|
2024-02-23 18:49:06 -05:00
|
|
|
-- GROUP BY optimization by reordering GROUP BY clauses
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
CREATE TABLE btg AS SELECT
|
2024-02-23 18:49:06 -05:00
|
|
|
i % 10 AS x,
|
|
|
|
|
i % 10 AS y,
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
'abc' || i % 10 AS z,
|
|
|
|
|
i AS w
|
2024-02-23 18:49:06 -05:00
|
|
|
FROM generate_series(1, 100) AS i;
|
|
|
|
|
CREATE INDEX btg_x_y_idx ON btg(x, y);
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
ANALYZE btg;
|
|
|
|
|
|
2024-02-23 18:49:06 -05:00
|
|
|
SET enable_hashagg = off;
|
|
|
|
|
SET enable_seqscan = off;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
2024-02-23 18:49:06 -05:00
|
|
|
-- Utilize the ordering of index scan to avoid a Sort operation
|
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT count(*) FROM btg GROUP BY y, x;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
|
|
|
|
-- Engage incremental sort
|
2024-02-23 18:49:06 -05:00
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT count(*) FROM btg GROUP BY z, y, w, x;
|
|
|
|
|
|
|
|
|
|
-- Utilize the ordering of subquery scan to avoid a Sort operation
|
|
|
|
|
EXPLAIN (COSTS OFF) SELECT count(*)
|
|
|
|
|
FROM (SELECT * FROM btg ORDER BY x, y, w, z) AS q1
|
|
|
|
|
GROUP BY w, x, z, y;
|
|
|
|
|
|
Consider explicit incremental sort for mergejoins
For a mergejoin, if the given outer path or inner path is not already
well enough ordered, we need to do an explicit sort. Currently, we
only consider explicit full sort and do not account for incremental
sort.
In this patch, for the outer path of a mergejoin, we choose to use
explicit incremental sort if it is enabled and there are presorted
keys. For the inner path, though, we cannot use incremental sort
because it does not support mark/restore at present.
The rationale is based on the assumption that incremental sort is
always faster than full sort when there are presorted keys, a premise
that has been applied in various parts of the code. In addition, the
current cost model tends to favor incremental sort as being cheaper
than full sort in the presence of presorted keys, making it reasonable
not to consider full sort in such cases.
It could be argued that what if a mergejoin with an incremental sort
as the outer path is selected as the inner path of another mergejoin.
However, this should not be a problem, because mergejoin itself does
not support mark/restore either, and we will add a Material node on
top of it anyway in this case (see final_cost_mergejoin).
There is one ensuing plan change in the regression tests, and we have
to modify that test case to ensure that it continues to test what it
is intended to.
No backpatch as this could result in plan changes.
Author: Richard Guo
Reviewed-by: David Rowley, Tomas Vondra
Discussion: https://postgr.es/m/CAMbWs49x425QrX7h=Ux05WEnt8GS757H-jOP3_xsX5t1FoUsZw@mail.gmail.com
2024-10-09 04:14:42 -04:00
|
|
|
-- Utilize the ordering of merge join to avoid a Sort operation
|
2024-02-23 18:49:06 -05:00
|
|
|
SET enable_hashjoin = off;
|
|
|
|
|
SET enable_nestloop = off;
|
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT count(*)
|
Consider explicit incremental sort for mergejoins
For a mergejoin, if the given outer path or inner path is not already
well enough ordered, we need to do an explicit sort. Currently, we
only consider explicit full sort and do not account for incremental
sort.
In this patch, for the outer path of a mergejoin, we choose to use
explicit incremental sort if it is enabled and there are presorted
keys. For the inner path, though, we cannot use incremental sort
because it does not support mark/restore at present.
The rationale is based on the assumption that incremental sort is
always faster than full sort when there are presorted keys, a premise
that has been applied in various parts of the code. In addition, the
current cost model tends to favor incremental sort as being cheaper
than full sort in the presence of presorted keys, making it reasonable
not to consider full sort in such cases.
It could be argued that what if a mergejoin with an incremental sort
as the outer path is selected as the inner path of another mergejoin.
However, this should not be a problem, because mergejoin itself does
not support mark/restore either, and we will add a Material node on
top of it anyway in this case (see final_cost_mergejoin).
There is one ensuing plan change in the regression tests, and we have
to modify that test case to ensure that it continues to test what it
is intended to.
No backpatch as this could result in plan changes.
Author: Richard Guo
Reviewed-by: David Rowley, Tomas Vondra
Discussion: https://postgr.es/m/CAMbWs49x425QrX7h=Ux05WEnt8GS757H-jOP3_xsX5t1FoUsZw@mail.gmail.com
2024-10-09 04:14:42 -04:00
|
|
|
FROM btg t1 JOIN btg t2 ON t1.w = t2.w AND t1.x = t2.x AND t1.z = t2.z
|
|
|
|
|
GROUP BY t1.w, t1.z, t1.x;
|
2024-02-23 18:49:06 -05:00
|
|
|
RESET enable_nestloop;
|
|
|
|
|
RESET enable_hashjoin;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
|
|
|
|
-- Should work with and without GROUP-BY optimization
|
2024-02-23 18:49:06 -05:00
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT count(*) FROM btg GROUP BY w, x, z, y ORDER BY y, x, z, w;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
|
|
|
|
-- Utilize incremental sort to make the ORDER BY rule a bit cheaper
|
2024-02-23 18:49:06 -05:00
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT count(*) FROM btg GROUP BY w, x, y, z ORDER BY x*x, z;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
2024-02-23 18:49:06 -05:00
|
|
|
-- Test the case where the number of incoming subtree path keys is more than
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
-- the number of grouping keys.
|
2024-02-23 18:49:06 -05:00
|
|
|
CREATE INDEX btg_y_x_w_idx ON btg(y, x, w);
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
EXPLAIN (VERBOSE, COSTS OFF)
|
2024-02-23 18:49:06 -05:00
|
|
|
SELECT y, x, array_agg(distinct w)
|
|
|
|
|
FROM btg WHERE y < 0 GROUP BY x, y;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
2024-02-23 18:49:06 -05:00
|
|
|
-- Ensure that we do not select the aggregate pathkeys instead of the grouping
|
|
|
|
|
-- pathkeys
|
2024-02-09 05:56:26 -05:00
|
|
|
CREATE TABLE group_agg_pk AS SELECT
|
|
|
|
|
i % 10 AS x,
|
|
|
|
|
i % 2 AS y,
|
|
|
|
|
i % 2 AS z,
|
|
|
|
|
2 AS w,
|
|
|
|
|
i % 10 AS f
|
|
|
|
|
FROM generate_series(1,100) AS i;
|
|
|
|
|
ANALYZE group_agg_pk;
|
|
|
|
|
SET enable_nestloop = off;
|
|
|
|
|
SET enable_hashjoin = off;
|
2024-02-23 18:49:06 -05:00
|
|
|
|
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT avg(c1.f ORDER BY c1.x, c1.y)
|
|
|
|
|
FROM group_agg_pk c1 JOIN group_agg_pk c2 ON c1.x = c2.x
|
|
|
|
|
GROUP BY c1.w, c1.z;
|
|
|
|
|
SELECT avg(c1.f ORDER BY c1.x, c1.y)
|
|
|
|
|
FROM group_agg_pk c1 JOIN group_agg_pk c2 ON c1.x = c2.x
|
2024-02-09 05:56:26 -05:00
|
|
|
GROUP BY c1.w, c1.z;
|
2024-02-23 18:49:06 -05:00
|
|
|
|
2024-06-06 06:41:34 -04:00
|
|
|
-- Pathkeys, built in a subtree, can be used to optimize GROUP-BY clause
|
|
|
|
|
-- ordering. Also, here we check that it doesn't depend on the initial clause
|
|
|
|
|
-- order in the GROUP-BY list.
|
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT c1.y,c1.x FROM group_agg_pk c1
|
|
|
|
|
JOIN group_agg_pk c2
|
|
|
|
|
ON c1.x = c2.x
|
|
|
|
|
GROUP BY c1.y,c1.x,c2.x;
|
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
|
SELECT c1.y,c1.x FROM group_agg_pk c1
|
|
|
|
|
JOIN group_agg_pk c2
|
|
|
|
|
ON c1.x = c2.x
|
|
|
|
|
GROUP BY c1.y,c2.x,c1.x;
|
|
|
|
|
|
2024-02-09 05:56:26 -05:00
|
|
|
RESET enable_nestloop;
|
|
|
|
|
RESET enable_hashjoin;
|
|
|
|
|
DROP TABLE group_agg_pk;
|
|
|
|
|
|
2024-04-18 15:28:07 -04:00
|
|
|
-- Test the case where the ordering of the scan matches the ordering within the
|
2024-02-23 18:49:06 -05:00
|
|
|
-- aggregate but cannot be found in the group-by list
|
2024-01-21 16:26:41 -05:00
|
|
|
CREATE TABLE agg_sort_order (c1 int PRIMARY KEY, c2 int);
|
2024-02-23 18:49:06 -05:00
|
|
|
CREATE UNIQUE INDEX agg_sort_order_c2_idx ON agg_sort_order(c2);
|
|
|
|
|
INSERT INTO agg_sort_order SELECT i, i FROM generate_series(1,100)i;
|
|
|
|
|
ANALYZE agg_sort_order;
|
|
|
|
|
|
|
|
|
|
EXPLAIN (COSTS OFF)
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
SELECT array_agg(c1 ORDER BY c2),c2
|
2024-01-21 16:26:41 -05:00
|
|
|
FROM agg_sort_order WHERE c2 < 100 GROUP BY c1 ORDER BY 2;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
2024-02-23 18:49:06 -05:00
|
|
|
DROP TABLE agg_sort_order CASCADE;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
2024-02-19 07:11:50 -05:00
|
|
|
DROP TABLE btg;
|
2024-02-23 18:49:06 -05:00
|
|
|
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
RESET enable_hashagg;
|
2024-02-23 18:49:06 -05:00
|
|
|
RESET enable_seqscan;
|
Explore alternative orderings of group-by pathkeys during optimization.
When evaluating a query with a multi-column GROUP BY clause, we can minimize
sort operations or avoid them if we synchronize the order of GROUP BY clauses
with the ORDER BY sort clause or sort order, which comes from the underlying
query tree. Grouping does not imply any ordering, so we can compare
the keys in arbitrary order, and a Hash Agg leverages this. But for Group Agg,
we simply compared keys in the order specified in the query. This commit
explores alternative ordering of the keys, trying to find a cheaper one.
The ordering of group keys may interact with other parts of the query, some of
which may not be known while planning the grouping. For example, there may be
an explicit ORDER BY clause or some other ordering-dependent operation higher up
in the query, and using the same ordering may allow using either incremental
sort or even eliminating the sort entirely.
The patch always keeps the ordering specified in the query, assuming the user
might have additional insights.
This introduces a new GUC enable_group_by_reordering so that the optimization
may be disabled if needed.
Discussion: https://postgr.es/m/7c79e6a5-8597-74e8-0671-1c39d124c9d6%40sigaev.ru
Author: Andrei Lepikhov, Teodor Sigaev
Reviewed-by: Tomas Vondra, Claudio Freire, Gavin Flower, Dmitry Dolgov
Reviewed-by: Robert Haas, Pavel Borisov, David Rowley, Zhihong Yu
Reviewed-by: Tom Lane, Alexander Korotkov, Richard Guo, Alena Rybakina
2024-01-21 15:21:36 -05:00
|
|
|
|
2017-11-23 20:13:09 -05:00
|
|
|
-- Secondly test the case of a parallel aggregate combiner function
|
|
|
|
|
-- returning NULL. For that use normal transition function, but a
|
|
|
|
|
-- combiner function returning NULL.
|
2021-03-15 06:27:08 -04:00
|
|
|
BEGIN;
|
2017-11-23 20:13:09 -05:00
|
|
|
CREATE FUNCTION balkifnull(int8, int8)
|
|
|
|
|
RETURNS int8
|
|
|
|
|
PARALLEL SAFE
|
|
|
|
|
STRICT
|
|
|
|
|
LANGUAGE plpgsql AS $$
|
|
|
|
|
BEGIN
|
|
|
|
|
IF $1 IS NULL THEN
|
|
|
|
|
RAISE 'erroneously called with NULL argument';
|
|
|
|
|
END IF;
|
|
|
|
|
RETURN NULL;
|
|
|
|
|
END$$;
|
|
|
|
|
|
Avoid unnecessary use of pg_strcasecmp for already-downcased identifiers.
We have a lot of code in which option names, which from the user's
viewpoint are logically keywords, are passed through the grammar as plain
identifiers, and then matched to string literals during command execution.
This approach avoids making words into lexer keywords unnecessarily. Some
places matched these strings using plain strcmp, some using pg_strcasecmp.
But the latter should be unnecessary since identifiers would have been
downcased on their way through the parser. Aside from any efficiency
concerns (probably not a big factor), the lack of consistency in this area
creates a hazard of subtle bugs due to different places coming to different
conclusions about whether two option names are the same or different.
Hence, standardize on using strcmp() to match any option names that are
expected to have been fed through the parser.
This does create a user-visible behavioral change, which is that while
formerly all of these would work:
alter table foo set (fillfactor = 50);
alter table foo set (FillFactor = 50);
alter table foo set ("fillfactor" = 50);
alter table foo set ("FillFactor" = 50);
now the last case will fail because that double-quoted identifier is
different from the others. However, none of our documentation says that
you can use a quoted identifier in such contexts at all, and we should
discourage doing so since it would break if we ever decide to parse such
constructs as true lexer keywords rather than poor man's substitutes.
So this shouldn't create a significant compatibility issue for users.
Daniel Gustafsson, reviewed by Michael Paquier, small changes by me
Discussion: https://postgr.es/m/29405B24-564E-476B-98C0-677A29805B84@yesql.se
2018-01-26 18:25:02 -05:00
|
|
|
CREATE AGGREGATE balk(int4)
|
|
|
|
|
(
|
2017-11-23 20:13:09 -05:00
|
|
|
SFUNC = int4_sum(int8, int4),
|
|
|
|
|
STYPE = int8,
|
|
|
|
|
COMBINEFUNC = balkifnull(int8, int8),
|
Avoid unnecessary use of pg_strcasecmp for already-downcased identifiers.
We have a lot of code in which option names, which from the user's
viewpoint are logically keywords, are passed through the grammar as plain
identifiers, and then matched to string literals during command execution.
This approach avoids making words into lexer keywords unnecessarily. Some
places matched these strings using plain strcmp, some using pg_strcasecmp.
But the latter should be unnecessary since identifiers would have been
downcased on their way through the parser. Aside from any efficiency
concerns (probably not a big factor), the lack of consistency in this area
creates a hazard of subtle bugs due to different places coming to different
conclusions about whether two option names are the same or different.
Hence, standardize on using strcmp() to match any option names that are
expected to have been fed through the parser.
This does create a user-visible behavioral change, which is that while
formerly all of these would work:
alter table foo set (fillfactor = 50);
alter table foo set (FillFactor = 50);
alter table foo set ("fillfactor" = 50);
alter table foo set ("FillFactor" = 50);
now the last case will fail because that double-quoted identifier is
different from the others. However, none of our documentation says that
you can use a quoted identifier in such contexts at all, and we should
discourage doing so since it would break if we ever decide to parse such
constructs as true lexer keywords rather than poor man's substitutes.
So this shouldn't create a significant compatibility issue for users.
Daniel Gustafsson, reviewed by Michael Paquier, small changes by me
Discussion: https://postgr.es/m/29405B24-564E-476B-98C0-677A29805B84@yesql.se
2018-01-26 18:25:02 -05:00
|
|
|
PARALLEL = SAFE,
|
2017-11-23 20:13:09 -05:00
|
|
|
INITCOND = '0'
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
-- force use of parallelism
|
|
|
|
|
ALTER TABLE tenk1 set (parallel_workers = 4);
|
|
|
|
|
SET LOCAL parallel_setup_cost=0;
|
|
|
|
|
SET LOCAL max_parallel_workers_per_gather=4;
|
|
|
|
|
|
2017-11-24 00:29:20 -05:00
|
|
|
EXPLAIN (COSTS OFF) SELECT balk(hundred) FROM tenk1;
|
|
|
|
|
SELECT balk(hundred) FROM tenk1;
|
2017-11-23 20:13:09 -05:00
|
|
|
|
|
|
|
|
ROLLBACK;
|
2018-06-21 16:18:33 -04:00
|
|
|
|
2023-04-16 14:16:40 -04:00
|
|
|
-- test multiple usage of an aggregate whose finalfn returns a R/W datum
|
|
|
|
|
BEGIN;
|
|
|
|
|
|
|
|
|
|
CREATE FUNCTION rwagg_sfunc(x anyarray, y anyarray) RETURNS anyarray
|
|
|
|
|
LANGUAGE plpgsql IMMUTABLE AS $$
|
|
|
|
|
BEGIN
|
|
|
|
|
RETURN array_fill(y[1], ARRAY[4]);
|
|
|
|
|
END;
|
|
|
|
|
$$;
|
|
|
|
|
|
|
|
|
|
CREATE FUNCTION rwagg_finalfunc(x anyarray) RETURNS anyarray
|
|
|
|
|
LANGUAGE plpgsql STRICT IMMUTABLE AS $$
|
|
|
|
|
DECLARE
|
|
|
|
|
res x%TYPE;
|
|
|
|
|
BEGIN
|
|
|
|
|
-- assignment is essential for this test, it expands the array to R/W
|
|
|
|
|
res := array_fill(x[1], ARRAY[4]);
|
|
|
|
|
RETURN res;
|
|
|
|
|
END;
|
|
|
|
|
$$;
|
|
|
|
|
|
|
|
|
|
CREATE AGGREGATE rwagg(anyarray) (
|
|
|
|
|
STYPE = anyarray,
|
|
|
|
|
SFUNC = rwagg_sfunc,
|
|
|
|
|
FINALFUNC = rwagg_finalfunc
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
CREATE FUNCTION eatarray(x real[]) RETURNS real[]
|
|
|
|
|
LANGUAGE plpgsql STRICT IMMUTABLE AS $$
|
|
|
|
|
BEGIN
|
|
|
|
|
x[1] := x[1] + 1;
|
|
|
|
|
RETURN x;
|
|
|
|
|
END;
|
|
|
|
|
$$;
|
|
|
|
|
|
|
|
|
|
SELECT eatarray(rwagg(ARRAY[1.0::real])), eatarray(rwagg(ARRAY[1.0::real]));
|
|
|
|
|
|
|
|
|
|
ROLLBACK;
|
|
|
|
|
|
2018-06-21 16:18:33 -04:00
|
|
|
-- test coverage for aggregate combine/serial/deserial functions
|
2021-03-15 06:27:08 -04:00
|
|
|
BEGIN;
|
2018-06-21 16:18:33 -04:00
|
|
|
|
|
|
|
|
SET parallel_setup_cost = 0;
|
|
|
|
|
SET parallel_tuple_cost = 0;
|
|
|
|
|
SET min_parallel_table_scan_size = 0;
|
|
|
|
|
SET max_parallel_workers_per_gather = 4;
|
2020-06-11 17:38:42 -04:00
|
|
|
SET parallel_leader_participation = off;
|
2018-06-21 16:18:33 -04:00
|
|
|
SET enable_indexonlyscan = off;
|
|
|
|
|
|
|
|
|
|
-- variance(int4) covers numeric_poly_combine
|
|
|
|
|
-- sum(int8) covers int8_avg_combine
|
Minimally fix partial aggregation for aggregates that don't have one argument.
For partial aggregation combine steps,
AggStatePerTrans->numTransInputs was set to the transition function's
number of inputs, rather than the combine function's number of
inputs (always 1).
That lead to partial aggregates with strict combine functions to
wrongly check for NOT NULL input as required by strictness. When the
aggregate wasn't exactly passed one argument, the strictness check was
either omitted (in the 0 args case) or too many arguments were
checked. In the latter case we'd read beyond the end of
FunctionCallInfoData->args (only in master).
AggStatePerTrans->numTransInputs actually has been wrong since since
9.6, where partial aggregates were added. But it turns out to not be
an active problem in 9.6 and 10, because numTransInputs wasn't used at
all for combine functions: Before c253b722f6 there simply was no NULL
check for the input to strict trans functions, and after that the
check was simply hardcoded for the right offset in fcinfo, as it's
done by code specific to combine functions.
In bf6c614a2f2 (11) the strictness check was generalized, with common
code doing the strictness checks for both plain and combine transition
functions, based on numTransInputs. For combine functions this lead to
not emitting an expression step to check for strict input in the 0
arguments case, and in the > 1 arguments case, we'd check too many
arguments.Due to the fact that the relevant fcinfo->isnull[2..] was
always zero-initialized (more or less by accident, by being part of
the AggStatePerTrans struct, which is palloc0'ed), there was no
observable damage in the latter case before a9c35cf85ca1f, we just
checked too many array elements.
Due to the changes in a9c35cf85ca1f, > 1 argument bug became visible,
because these days fcinfo is a) dynamically allocated without being
zeroed b) exactly the length required for the number of specified
arguments (hardcoded to 2 in this case).
This commit only contains a fairly minimal fix, setting numTransInputs
to a hardcoded 1 when building a pertrans for a combine function. It
seems likely that we'll want to clean this up further (e.g. the
arguments build_pertrans_for_aggref() aren't particularly meaningful
for combine functions). But the wrap date for 12 beta1 is coming up
fast, so it seems good to have a minimal fix in place.
Backpatch to 11. While AggStatePerTrans->numTransInputs was set
wrongly before that, the value was not used for combine functions.
Reported-By: Rajkumar Raghuwanshi
Diagnosed-By: Kyotaro Horiguchi, Jeevan Chalke, Andres Freund, David Rowley
Author: David Rowley, Kyotaro Horiguchi, Andres Freund
Discussion: https://postgr.es/m/CAKcux6=uZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew@mail.gmail.com
2019-05-19 21:01:06 -04:00
|
|
|
-- regr_count(float8, float8) covers int8inc_float8_float8 and aggregates with > 1 arg
|
|
|
|
|
EXPLAIN (COSTS OFF, VERBOSE)
|
2020-06-11 17:38:42 -04:00
|
|
|
SELECT variance(unique1::int4), sum(unique1::int8), regr_count(unique1::float8, unique1::float8)
|
|
|
|
|
FROM (SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1) u;
|
|
|
|
|
|
|
|
|
|
SELECT variance(unique1::int4), sum(unique1::int8), regr_count(unique1::float8, unique1::float8)
|
|
|
|
|
FROM (SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1) u;
|
|
|
|
|
|
|
|
|
|
-- variance(int8) covers numeric_combine
|
|
|
|
|
-- avg(numeric) covers numeric_avg_combine
|
|
|
|
|
EXPLAIN (COSTS OFF, VERBOSE)
|
|
|
|
|
SELECT variance(unique1::int8), avg(unique1::numeric)
|
|
|
|
|
FROM (SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1) u;
|
|
|
|
|
|
|
|
|
|
SELECT variance(unique1::int8), avg(unique1::numeric)
|
|
|
|
|
FROM (SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1
|
|
|
|
|
UNION ALL SELECT * FROM tenk1) u;
|
2018-06-21 16:18:33 -04:00
|
|
|
|
|
|
|
|
ROLLBACK;
|
2018-07-04 20:36:01 -04:00
|
|
|
|
|
|
|
|
-- test coverage for dense_rank
|
|
|
|
|
SELECT dense_rank(x) WITHIN GROUP (ORDER BY x) FROM (VALUES (1),(1),(2),(2),(3),(3)) v(x) GROUP BY (x) ORDER BY 1;
|
2018-11-03 17:35:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Ensure that the STRICT checks for aggregates does not take NULLness
|
|
|
|
|
-- of ORDER BY columns into account. See bug report around
|
|
|
|
|
-- 2a505161-2727-2473-7c46-591ed108ac52@email.cz
|
|
|
|
|
SELECT min(x ORDER BY y) FROM (VALUES(1, NULL)) AS d(x,y);
|
|
|
|
|
SELECT min(x ORDER BY y) FROM (VALUES(1, 2)) AS d(x,y);
|
2019-01-17 00:33:01 -05:00
|
|
|
|
|
|
|
|
-- check collation-sensitive matching between grouping expressions
|
|
|
|
|
select v||'a', case v||'a' when 'aa' then 1 else 0 end, count(*)
|
|
|
|
|
from unnest(array['a','b']) u(v)
|
|
|
|
|
group by v||'a' order by 1;
|
|
|
|
|
select v||'a', case when v||'a' = 'aa' then 1 else 0 end, count(*)
|
|
|
|
|
from unnest(array['a','b']) u(v)
|
|
|
|
|
group by v||'a' order by 1;
|
2019-05-23 10:26:01 -04:00
|
|
|
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
--
|
|
|
|
|
-- Hash Aggregation Spill tests
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
set enable_sort=false;
|
|
|
|
|
set work_mem='64kB';
|
|
|
|
|
|
|
|
|
|
select unique1, count(*), sum(twothousand) from tenk1
|
|
|
|
|
group by unique1
|
|
|
|
|
having sum(fivethous) > 4975
|
|
|
|
|
order by sum(twothousand);
|
|
|
|
|
|
|
|
|
|
set work_mem to default;
|
|
|
|
|
set enable_sort to default;
|
|
|
|
|
|
|
|
|
|
--
|
|
|
|
|
-- Compare results between plans using sorting and plans using hash
|
|
|
|
|
-- aggregation. Force spilling in both cases by setting work_mem low.
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
set work_mem='64kB';
|
|
|
|
|
|
2020-06-11 14:58:16 -04:00
|
|
|
create table agg_data_2k as
|
|
|
|
|
select g from generate_series(0, 1999) g;
|
|
|
|
|
analyze agg_data_2k;
|
|
|
|
|
|
|
|
|
|
create table agg_data_20k as
|
|
|
|
|
select g from generate_series(0, 19999) g;
|
|
|
|
|
analyze agg_data_20k;
|
|
|
|
|
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
-- Produce results with sorting.
|
|
|
|
|
|
|
|
|
|
set enable_hashagg = false;
|
|
|
|
|
|
|
|
|
|
set jit_above_cost = 0;
|
|
|
|
|
|
|
|
|
|
explain (costs off)
|
2020-03-23 21:55:12 -04:00
|
|
|
select g%10000 as c1, sum(g::numeric) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_20k group by g%10000;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
create table agg_group_1 as
|
2020-03-23 21:55:12 -04:00
|
|
|
select g%10000 as c1, sum(g::numeric) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_20k group by g%10000;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
create table agg_group_2 as
|
|
|
|
|
select * from
|
|
|
|
|
(values (100), (300), (500)) as r(a),
|
|
|
|
|
lateral (
|
|
|
|
|
select (g/2)::numeric as c1,
|
|
|
|
|
array_agg(g::numeric) as c2,
|
|
|
|
|
count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_2k
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
where g < r.a
|
|
|
|
|
group by g/2) as s;
|
|
|
|
|
|
|
|
|
|
set jit_above_cost to default;
|
|
|
|
|
|
|
|
|
|
create table agg_group_3 as
|
|
|
|
|
select (g/2)::numeric as c1, sum(7::int4) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_2k group by g/2;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
create table agg_group_4 as
|
|
|
|
|
select (g/2)::numeric as c1, array_agg(g::numeric) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_2k group by g/2;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
-- Produce results with hash aggregation
|
|
|
|
|
|
|
|
|
|
set enable_hashagg = true;
|
|
|
|
|
set enable_sort = false;
|
|
|
|
|
|
|
|
|
|
set jit_above_cost = 0;
|
|
|
|
|
|
|
|
|
|
explain (costs off)
|
2020-03-23 21:55:12 -04:00
|
|
|
select g%10000 as c1, sum(g::numeric) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_20k group by g%10000;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
create table agg_hash_1 as
|
2020-03-23 21:55:12 -04:00
|
|
|
select g%10000 as c1, sum(g::numeric) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_20k group by g%10000;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
create table agg_hash_2 as
|
|
|
|
|
select * from
|
|
|
|
|
(values (100), (300), (500)) as r(a),
|
|
|
|
|
lateral (
|
|
|
|
|
select (g/2)::numeric as c1,
|
|
|
|
|
array_agg(g::numeric) as c2,
|
|
|
|
|
count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_2k
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
where g < r.a
|
|
|
|
|
group by g/2) as s;
|
|
|
|
|
|
|
|
|
|
set jit_above_cost to default;
|
|
|
|
|
|
|
|
|
|
create table agg_hash_3 as
|
|
|
|
|
select (g/2)::numeric as c1, sum(7::int4) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_2k group by g/2;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
create table agg_hash_4 as
|
|
|
|
|
select (g/2)::numeric as c1, array_agg(g::numeric) as c2, count(*) as c3
|
2020-06-11 14:58:16 -04:00
|
|
|
from agg_data_2k group by g/2;
|
Disk-based Hash Aggregation.
While performing hash aggregation, track memory usage when adding new
groups to a hash table. If the memory usage exceeds work_mem, enter
"spill mode".
In spill mode, new groups are not created in the hash table(s), but
existing groups continue to be advanced if input tuples match. Tuples
that would cause a new group to be created are instead spilled to a
logical tape to be processed later.
The tuples are spilled in a partitioned fashion. When all tuples from
the outer plan are processed (either by advancing the group or
spilling the tuple), finalize and emit the groups from the hash
table. Then, create new batches of work from the spilled partitions,
and select one of the saved batches and process it (possibly spilling
recursively).
Author: Jeff Davis
Reviewed-by: Tomas Vondra, Adam Lee, Justin Pryzby, Taylor Vesely, Melanie Plageman
Discussion: https://postgr.es/m/507ac540ec7c20136364b5272acbcd4574aa76ef.camel@j-davis.com
2020-03-18 18:42:02 -04:00
|
|
|
|
|
|
|
|
set enable_sort = true;
|
|
|
|
|
set work_mem to default;
|
|
|
|
|
|
|
|
|
|
-- Compare group aggregation results to hash aggregation results
|
|
|
|
|
|
|
|
|
|
(select * from agg_hash_1 except select * from agg_group_1)
|
|
|
|
|
union all
|
|
|
|
|
(select * from agg_group_1 except select * from agg_hash_1);
|
|
|
|
|
|
|
|
|
|
(select * from agg_hash_2 except select * from agg_group_2)
|
|
|
|
|
union all
|
|
|
|
|
(select * from agg_group_2 except select * from agg_hash_2);
|
|
|
|
|
|
|
|
|
|
(select * from agg_hash_3 except select * from agg_group_3)
|
|
|
|
|
union all
|
|
|
|
|
(select * from agg_group_3 except select * from agg_hash_3);
|
|
|
|
|
|
|
|
|
|
(select * from agg_hash_4 except select * from agg_group_4)
|
|
|
|
|
union all
|
|
|
|
|
(select * from agg_group_4 except select * from agg_hash_4);
|
|
|
|
|
|
|
|
|
|
drop table agg_group_1;
|
|
|
|
|
drop table agg_group_2;
|
|
|
|
|
drop table agg_group_3;
|
|
|
|
|
drop table agg_group_4;
|
|
|
|
|
drop table agg_hash_1;
|
|
|
|
|
drop table agg_hash_2;
|
|
|
|
|
drop table agg_hash_3;
|
|
|
|
|
drop table agg_hash_4;
|