[no release] Testing regression tests

[fulghum]

No description provided.

[github-actions]

	Main	PR
covering_index_scan_postgres	1337.95/s	1347.81/s	+0.7%
index_join_postgres	188.62/s	190.90/s	+1.2%
index_join_scan_postgres	198.68/s	199.66/s	+0.4%
index_scan_postgres	11.89/s	12.21/s	+2.6%
oltp_point_select	2475.78/s	2511.79/s	+1.4%
oltp_read_only	1862.98/s	1865.36/s	+0.1%
select_random_points	129.64/s	131.10/s	+1.1%
select_random_ranges	1074.71/s	1077.05/s	+0.2%
table_scan_postgres	11.63/s	11.92/s	+2.4%
types_table_scan_postgres	5.35/s	5.49/s	+2.6%

[github-actions]

	Main	PR
Total	42090	42090
Successful	17966	18014
Failures	24124	24076
Partial Successes1	5375	5373

	Main	PR
Successful	42.6847%	42.7988%
Failures	57.3153%	57.2012%

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

domain

QUERY: create temp table dtest(f1 dtop);

QUERY: drop table dtest;

QUERY: create domain str_domain as text not null;

QUERY: create table domain_test (a int, b int);

QUERY: insert into domain_test values (1, 2);

QUERY: insert into domain_test values (1, 2);

QUERY: create domain pos_int as int4 check (value > 0) not null;

QUERY: create function doubledecrement(p1 pos_int) returns pos_int as $$
declare v pos_int;
begin
    return p1;
end$$ language plpgsql;

QUERY: create or replace function doubledecrement(p1 pos_int) returns pos_int as $$
declare v pos_int := 0;
begin
    return p1;
end$$ language plpgsql;

QUERY: create or replace function doubledecrement(p1 pos_int) returns pos_int as $$
declare v pos_int := 1;
begin
    v := p1 - 1;
    return v - 1;
end$$ language plpgsql;

QUERY: create type ddtest1 as (f1 posint);

QUERY: create table ddtest2(f1 ddtest1);

QUERY: drop table ddtest2;

QUERY: create table ddtest2(f1 ddtest1[]);

QUERY: drop table ddtest2;

QUERY: create domain ddtest1d as ddtest1;

QUERY: create table ddtest2(f1 ddtest1d);

QUERY: drop table ddtest2;

QUERY: drop domain ddtest1d;

QUERY: create domain ddtest1d as ddtest1[];

QUERY: create table ddtest2(f1 ddtest1d);

QUERY: drop table ddtest2;

QUERY: drop domain ddtest1d;

QUERY: create domain posint2 as posint check (value % 2 = 0);

QUERY: create table ddtest2(f1 posint2);

QUERY: drop table ddtest2;

QUERY: drop type ddtest1;

QUERY: create or replace function array_elem_check(numeric) returns numeric as $$
declare
  x numeric(4,2)[1];
begin
  x[1] := $1;
  return x[1];
end$$ language plpgsql;

QUERY: create domain mynums as numeric(4,2)[1];

QUERY: create or replace function array_elem_check(numeric) returns numeric as $$
declare
  x mynums;
begin
  x[1] := $1;
  return x[1];
end$$ language plpgsql;

QUERY: create domain mynums2 as mynums;

QUERY: create or replace function array_elem_check(numeric) returns numeric as $$
declare
  x mynums2;
begin
  x[1] := $1;
  return x[1];
end$$ language plpgsql;

QUERY: drop function array_elem_check(numeric);

QUERY: create domain orderedpair as int[2] check (value[1] < value[2]);

QUERY: create temp table op (f1 orderedpair);

QUERY: create or replace function array_elem_check(int) returns int as $$
declare
  x orderedpair := '{1,2}';
begin
  x[2] := $1;
  return x[2];
end$$ language plpgsql;

QUERY: drop function array_elem_check(int);

QUERY: create domain di as int;

QUERY: create function dom_check(int) returns di as $$
declare d di;
begin
  d := $1::di;
  return d;
end
$$ language plpgsql immutable;

QUERY: create or replace function dom_check(int) returns di as $$
declare d di;
begin
  d := $1;
  return d;
end
$$ language plpgsql immutable;

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. ↩