update decimal.Decimal to *apd.Decimal

[jennifersp]

Depends on dolthub/go-mysql-server#3532 and dolthub/dolt#10990

[github-actions]

	Main	PR
covering_index_scan_postgres	1344.45/s	1334.08/s	-0.8%
index_join_postgres	188.57/s	186.04/s	-1.4%
index_join_scan_postgres	197.16/s	195.72/s	-0.8%
index_scan_postgres	12.15/s	12.23/s	+0.6%
oltp_point_select	2490.54/s	2441.50/s	-2.0%
oltp_read_only	1858.63/s	1857.88/s	-0.1%
select_random_points	127.04/s	129.81/s	+2.1%
select_random_ranges	1065.88/s	1068.93/s	+0.2%
table_scan_postgres	11.67/s	11.98/s	+2.6%
types_table_scan_postgres	5.35/s	5.55/s	+3.7%

[zachmu]

Good start, but we need to standardize these values across all three packages. See specific comments.

Final PR should have tests of storing NaN, Infinity, etc. in column values and reading them back.

[github-actions]

	Main	PR
Total	42090	42090
Successful	18017	18105
Failures	24073	23985
Partial Successes1	5372	5377

	Main	PR
Successful	42.8059%	43.0150%
Failures	57.1941%	56.9850%

${\color{lightgreen}Progressions (93)}$

float4

QUERY: SELECT 'nan'::numeric::float4;

float8

QUERY: SELECT 'nan'::numeric::float8;

numeric

QUERY: INSERT INTO num_exp_div VALUES (0,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (0,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (1,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (1,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (2,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (2,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (3,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (3,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (4,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (4,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (5,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (5,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (6,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (6,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (7,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (7,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (8,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (8,1,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (9,0,'NaN');

QUERY: INSERT INTO num_exp_div VALUES (9,1,'NaN');

QUERY: INSERT INTO num_exp_ln VALUES (0,'NaN');

QUERY: INSERT INTO num_exp_ln VALUES (1,'NaN');

QUERY: INSERT INTO num_exp_log10 VALUES (0,'NaN');

QUERY: INSERT INTO num_exp_log10 VALUES (1,'NaN');

QUERY: INSERT INTO num_exp_power_10_ln VALUES (0,'NaN');

QUERY: INSERT INTO num_exp_power_10_ln VALUES (1,'NaN');

QUERY: SELECT 'nan'::numeric / '0';

QUERY: SELECT 'nan'::numeric % '0';

QUERY: SELECT div('nan'::numeric, '0');

QUERY: WITH v(x) AS
  (VALUES('0'::numeric),('1'),('-1'),('4.2'),('-7.777'),('1e340'),('-1e340'),
         ('inf'),('-inf'),('nan'),
         ('inf'),('-inf'),('nan'))
SELECT substring(x::text, 1, 32)
FROM v ORDER BY x;

QUERY: SELECT power('-2'::numeric, '3');

QUERY: SELECT power('-2'::numeric, '3.3');

QUERY: SELECT power('-2'::numeric, '-1.5');

QUERY: SELECT power('inf'::numeric, '-2');

QUERY: SELECT power('inf'::numeric, '-inf');

QUERY: SELECT power('-inf'::numeric, '2');

QUERY: SELECT power('-inf'::numeric, '3');

QUERY: SELECT power('-inf'::numeric, '-2');

Footnotes

1. These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct. ↩

[zachmu]

LGTM