2025-01-05 17:28:23.885 GMT postmaster[6752] LOG: starting PostgreSQL 18devel on x86_64-windows, compiled by msvc-19.29.30157, 64-bit
2025-01-05 17:28:23.888 GMT postmaster[6752] LOG: listening on Unix socket "c:/cirrus/.s.PGSQL.40000"
2025-01-05 17:28:23.939 GMT startup[2352] LOG: database system was shut down at 2025-01-05 17:25:50 GMT
2025-01-05 17:28:23.963 GMT client backend[6916] [unknown] FATAL: the database system is starting up
2025-01-05 17:28:23.965 GMT postmaster[6752] LOG: database system is ready to accept connections
2025-01-05 17:28:24.933 GMT client backend[5840] pg_regress/plpgsql_array ERROR: malformed array literal: "4"
2025-01-05 17:28:24.933 GMT client backend[5840] pg_regress/plpgsql_array DETAIL: Array value must start with "{" or dimension information.
2025-01-05 17:28:24.933 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment
2025-01-05 17:28:24.933 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[];
begin a[1:2] := 4; raise notice 'a = %', a; end$$;
2025-01-05 17:28:24.935 GMT client backend[5840] pg_regress/plpgsql_array ERROR: cannot assign to field "i" of column "a" because its type complex[] is not a composite type at character 1
2025-01-05 17:28:24.935 GMT client backend[5840] pg_regress/plpgsql_array QUERY: a[1:2].i := array[11,12]
2025-01-05 17:28:24.935 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment
2025-01-05 17:28:24.935 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$ declare a complex[];
begin a[1:2].i := array[11,12]; raise notice 'a = %', a; end$$;
2025-01-05 17:28:24.941 GMT client backend[5840] pg_regress/plpgsql_array ERROR: assignment source returned 0 columns
2025-01-05 17:28:24.941 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: PL/pgSQL assignment "a := from onecol"
PL/pgSQL function inline_code_block line 2 at assignment
2025-01-05 17:28:24.941 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[];
begin a := from onecol; raise notice 'a = %', a; end$$;
2025-01-05 17:28:24.942 GMT client backend[5840] pg_regress/plpgsql_array ERROR: assignment source returned 2 columns
2025-01-05 17:28:24.942 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: PL/pgSQL assignment "a := f1, f1 from onecol"
PL/pgSQL function inline_code_block line 2 at assignment
2025-01-05 17:28:24.942 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[];
begin a := f1, f1 from onecol; raise notice 'a = %', a; end$$;
2025-01-05 17:28:24.942 GMT client backend[5840] pg_regress/plpgsql_array ERROR: query returned more than one row
2025-01-05 17:28:24.942 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: query: a := f1 from onecol
PL/pgSQL function inline_code_block line 2 at assignment
2025-01-05 17:28:24.942 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[];
begin a := f1 from onecol; raise notice 'a = %', a; end$$;
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array ERROR: cannot subscript type real because it does not support subscripting at character 1
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array QUERY: a[1] := 2
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$ declare a real;
begin a[1] := 2; raise notice 'a = %', a; end$$;
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array ERROR: cannot subscript type double precision because it does not support subscripting at character 1
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array QUERY: a.r[1] := 2
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment
2025-01-05 17:28:24.943 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$ declare a complex;
begin a.r[1] := 2; raise notice 'a = %', a; end$$;
2025-01-05 17:28:24.946 GMT client backend[5840] pg_regress/plpgsql_array ERROR: could not find array type for data type pg_node_tree
2025-01-05 17:28:24.946 GMT client backend[5840] pg_regress/plpgsql_array CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 4
2025-01-05 17:28:24.946 GMT client backend[5840] pg_regress/plpgsql_array STATEMENT: do $$
declare
v pg_node_tree;
v1 v%type[];
begin
end;
$$;
2025-01-05 17:28:25.444 GMT client backend[5904] pg_regress/plpgsql_cache ERROR: type of parameter 4 (double precision) does not match that when preparing the plan (integer)
2025-01-05 17:28:25.444 GMT client backend[5904] pg_regress/plpgsql_cache CONTEXT: PL/pgSQL function c_sillyaddone(integer) line 1 at RETURN
2025-01-05 17:28:25.444 GMT client backend[5904] pg_regress/plpgsql_cache STATEMENT: select c_sillyaddone(42);
2025-01-05 17:28:25.447 GMT client backend[5904] pg_regress/plpgsql_cache ERROR: type of parameter 5 (numeric) does not match that when preparing the plan (integer)
2025-01-05 17:28:25.447 GMT client backend[5904] pg_regress/plpgsql_cache CONTEXT: SQL statement "select pg_typeof(r.a)"
PL/pgSQL function show_result_type(text) line 7 at SQL statement
2025-01-05 17:28:25.447 GMT client backend[5904] pg_regress/plpgsql_cache STATEMENT: select show_result_type('select 2.0 as a');
2025-01-05 17:28:25.752 GMT client backend[2660] pg_regress/plpgsql_call ERROR: RETURN cannot have a parameter in a procedure at character 71
2025-01-05 17:28:25.752 GMT client backend[2660] pg_regress/plpgsql_call STATEMENT: CREATE PROCEDURE test_proc2()
LANGUAGE plpgsql
AS $$
BEGIN
RETURN 5;
END;
$$;
2025-01-05 17:28:25.773 GMT client backend[2660] pg_regress/plpgsql_call ERROR: procedure parameter "b" is an output parameter but corresponding argument is not writable
2025-01-05 17:28:25.773 GMT client backend[2660] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 6 at CALL
2025-01-05 17:28:25.773 GMT client backend[2660] pg_regress/plpgsql_call STATEMENT: DO
LANGUAGE plpgsql
$$
DECLARE
x int := 3;
y int := 4;
BEGIN
CALL test_proc6(2, x + 1, y); -- error
RAISE INFO 'x = %, y = %', x, y;
END;
$$;
2025-01-05 17:28:25.773 GMT client backend[2660] pg_regress/plpgsql_call ERROR: variable "x" is declared CONSTANT
2025-01-05 17:28:25.773 GMT client backend[2660] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 6 at CALL
2025-01-05 17:28:25.773 GMT client backend[2660] pg_regress/plpgsql_call STATEMENT: DO
LANGUAGE plpgsql
$$
DECLARE
x constant int := 3;
y int := 4;
BEGIN
CALL test_proc6(2, x, y); -- error because x is constant
END;
$$;
2025-01-05 17:28:25.784 GMT client backend[2660] pg_regress/plpgsql_call ERROR: procedure parameter "c" is an output parameter but corresponding argument is not writable
2025-01-05 17:28:25.784 GMT client backend[2660] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 5 at CALL
2025-01-05 17:28:25.784 GMT client backend[2660] pg_regress/plpgsql_call STATEMENT: DO $$
DECLARE _a int; _b int; _c int;
BEGIN
_a := 10; _b := 30; _c := 50;
CALL test_proc8c(_a, _b); -- fail, no output argument for c
RAISE NOTICE '_a: %, _b: %, _c: %', _a, _b, _c;
END
$$;
2025-01-05 17:28:25.784 GMT client backend[2660] pg_regress/plpgsql_call ERROR: procedure parameter "c" is an output parameter but corresponding argument is not writable
2025-01-05 17:28:25.784 GMT client backend[2660] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 5 at CALL
2025-01-05 17:28:25.784 GMT client backend[2660] pg_regress/plpgsql_call STATEMENT: DO $$
DECLARE _a int; _b int; _c int;
BEGIN
_a := 10; _b := 30; _c := 50;
CALL test_proc8c(_a, b => _b); -- fail, no output argument for c
RAISE NOTICE '_a: %, _b: %, _c: %', _a, _b, _c;
END
$$;
2025-01-05 17:28:25.792 GMT client backend[2660] pg_regress/plpgsql_call ERROR: procedure test_proc12(integer, integer, text[]) does not exist at character 6
2025-01-05 17:28:25.792 GMT client backend[2660] pg_regress/plpgsql_call HINT: No procedure matches the given name and argument types. You might need to add explicit type casts.
2025-01-05 17:28:25.792 GMT client backend[2660] pg_regress/plpgsql_call QUERY: CALL test_proc12(_a, _b, _c)
2025-01-05 17:28:25.792 GMT client backend[2660] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 5 at CALL
2025-01-05 17:28:25.792 GMT client backend[2660] pg_regress/plpgsql_call STATEMENT: DO $$
DECLARE _a int; _b int; _c text[];
BEGIN
_a := 10;
CALL test_proc12(_a, _b, _c); -- error
RAISE NOTICE '_a: %, _b: %, _c: %', _a, _b, _c;
END
$$;
2025-01-05 17:28:25.802 GMT client backend[2660] pg_regress/plpgsql_call ERROR: procedure parameter "v_text" is an output parameter but corresponding argument is not writable
2025-01-05 17:28:25.802 GMT client backend[2660] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 6 at CALL
2025-01-05 17:28:25.802 GMT client backend[2660] pg_regress/plpgsql_call STATEMENT: DO $$
DECLARE
v_Text text;
v_cnt integer := 42;
BEGIN
CALL p1(v_cnt := v_cnt); -- error, must supply something for v_Text
RAISE NOTICE '%', v_Text;
END;
$$;
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control ERROR: BY value of FOR loop must be greater than zero
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function inline_code_block line 3 at FOR with integer loop variable
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: do $$
begin
for i in 1..3 by 0 loop
raise notice '1..3 by 0: i = %', i;
end loop;
end$$;
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control ERROR: BY value of FOR loop must be greater than zero
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function inline_code_block line 3 at FOR with integer loop variable
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: do $$
begin
for i in 1..3 by -1 loop
raise notice '1..3 by -1: i = %', i;
end loop;
end$$;
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control ERROR: BY value of FOR loop must be greater than zero
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function inline_code_block line 3 at FOR with integer loop variable
2025-01-05 17:28:26.055 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: do $$
begin
for i in reverse 1..3 by -1 loop
raise notice 'reverse 1..3 by -1: i = %', i;
end loop;
end$$;
2025-01-05 17:28:26.069 GMT client backend[5368] pg_regress/plpgsql_control ERROR: CONTINUE cannot be used outside a loop at character 78
2025-01-05 17:28:26.069 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function continue_error1() returns void as $$
begin
begin
continue;
end;
end;
$$ language plpgsql;
2025-01-05 17:28:26.070 GMT client backend[5368] pg_regress/plpgsql_control ERROR: EXIT cannot be used outside a loop, unless it has a label at character 74
2025-01-05 17:28:26.070 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function exit_error1() returns void as $$
begin
begin
exit;
end;
end;
$$ language plpgsql;
2025-01-05 17:28:26.071 GMT client backend[5368] pg_regress/plpgsql_control ERROR: there is no label "no_such_label" attached to any block or loop enclosing this statement at character 104
2025-01-05 17:28:26.071 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function continue_error2() returns void as $$
begin
begin
loop
continue no_such_label;
end loop;
end;
end;
$$ language plpgsql;
2025-01-05 17:28:26.071 GMT client backend[5368] pg_regress/plpgsql_control ERROR: there is no label "no_such_label" attached to any block or loop enclosing this statement at character 96
2025-01-05 17:28:26.071 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function exit_error2() returns void as $$
begin
begin
loop
exit no_such_label;
end loop;
end;
end;
$$ language plpgsql;
2025-01-05 17:28:26.071 GMT client backend[5368] pg_regress/plpgsql_control ERROR: block label "begin_block1" cannot be used in CONTINUE at character 125
2025-01-05 17:28:26.071 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function continue_error3() returns void as $$
begin
<<begin_block1>>
begin
loop
continue begin_block1;
end loop;
end;
end;
$$ language plpgsql;
2025-01-05 17:28:26.074 GMT client backend[5368] pg_regress/plpgsql_control ERROR: end label "flbl1" specified for unlabeled block at character 101
2025-01-05 17:28:26.074 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function end_label2() returns void as $$
begin
for _i in 1 .. 10 loop
exit;
end loop flbl1;
end;
$$ language plpgsql;
2025-01-05 17:28:26.074 GMT client backend[5368] pg_regress/plpgsql_control ERROR: end label "outer_label" differs from block's label "inner_label" at character 135
2025-01-05 17:28:26.074 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function end_label3() returns void as $$
<<outer_label>>
begin
<<inner_label>>
for _i in 1 .. 10 loop
exit;
end loop outer_label;
end;
$$ language plpgsql;
2025-01-05 17:28:26.075 GMT client backend[5368] pg_regress/plpgsql_control ERROR: end label "outer_label" specified for unlabeled block at character 117
2025-01-05 17:28:26.075 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: create function end_label4() returns void as $$
<<outer_label>>
begin
for _i in 1 .. 10 loop
exit;
end loop outer_label;
end;
$$ language plpgsql;
2025-01-05 17:28:26.083 GMT client backend[5368] pg_regress/plpgsql_control ERROR: case not found
2025-01-05 17:28:26.083 GMT client backend[5368] pg_regress/plpgsql_control HINT: CASE statement is missing ELSE part.
2025-01-05 17:28:26.083 GMT client backend[5368] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function case_test(bigint) line 5 at CASE
2025-01-05 17:28:26.083 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: select case_test(5);
2025-01-05 17:28:26.085 GMT client backend[5368] pg_regress/plpgsql_control ERROR: case not found
2025-01-05 17:28:26.085 GMT client backend[5368] pg_regress/plpgsql_control HINT: CASE statement is missing ELSE part.
2025-01-05 17:28:26.085 GMT client backend[5368] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function case_test(bigint) line 5 at CASE
2025-01-05 17:28:26.085 GMT client backend[5368] pg_regress/plpgsql_control STATEMENT: select case_test(13);
2025-01-05 17:28:26.256 GMT client backend[2324] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL
2025-01-05 17:28:26.256 GMT client backend[2324] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at SQL statement
2025-01-05 17:28:26.256 GMT client backend[2324] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
COPY copy1 TO stdout;
END;
$$;
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at SQL statement
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
COPY copy1 FROM stdin;
END;
$$;
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at EXECUTE
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
EXECUTE 'COPY copy1 TO stdout';
END;
$$;
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at EXECUTE
2025-01-05 17:28:26.257 GMT client backend[2324] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
EXECUTE 'COPY copy1 FROM stdin';
END;
$$;
2025-01-05 17:28:26.383 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check"
2025-01-05 17:28:26.383 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_booltrue(false, true);
2025-01-05 17:28:26.383 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check"
2025-01-05 17:28:26.383 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_booltrue(booltrue,boolean) while casting return value to function's return type
2025-01-05 17:28:26.383 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_booltrue(true, false);
2025-01-05 17:28:26.385 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check"
2025-01-05 17:28:26.385 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_booltrue(boolean,boolean) line 2 during statement block local variable initialization
2025-01-05 17:28:26.385 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_booltrue(false, true);
2025-01-05 17:28:26.385 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check"
2025-01-05 17:28:26.385 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_booltrue(boolean,boolean) line 4 at assignment
2025-01-05 17:28:26.385 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_booltrue(true, false);
2025-01-05 17:28:26.387 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check"
2025-01-05 17:28:26.387 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_uint2(uint2,integer) while casting return value to function's return type
2025-01-05 17:28:26.387 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_uint2(100::uint2, -50);
2025-01-05 17:28:26.389 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check"
2025-01-05 17:28:26.389 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_uint2(integer,integer) line 4 at assignment
2025-01-05 17:28:26.389 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_uint2(100, -50);
2025-01-05 17:28:26.389 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check"
2025-01-05 17:28:26.389 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_uint2(integer,integer) line 2 during statement block local variable initialization
2025-01-05 17:28:26.389 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_uint2(-100, 50);
2025-01-05 17:28:26.391 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.391 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_nnint(null, 20);
2025-01-05 17:28:26.391 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.391 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_nnint(nnint,integer) while casting return value to function's return type
2025-01-05 17:28:26.391 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_nnint(10, null);
2025-01-05 17:28:26.392 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.392 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint(integer,integer) line 2 during statement block local variable initialization
2025-01-05 17:28:26.392 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint(null, 20);
2025-01-05 17:28:26.392 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.392 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint(integer,integer) line 4 at assignment
2025-01-05 17:28:26.392 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint(10, null);
2025-01-05 17:28:26.395 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check"
2025-01-05 17:28:26.395 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_array_domain_check_violation() while casting return value to function's return type
2025-01-05 17:28:26.395 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_array_domain_check_violation();
2025-01-05 17:28:26.396 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check"
2025-01-05 17:28:26.396 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_pair_domain(integer,integer,integer) line 4 at assignment
2025-01-05 17:28:26.396 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_pair_domain(1,2,0);
2025-01-05 17:28:26.396 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check"
2025-01-05 17:28:26.396 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_pair_domain(integer,integer,integer) line 2 during statement block local variable initialization
2025-01-05 17:28:26.396 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_pair_domain(2,1,3);
2025-01-05 17:28:26.398 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check"
2025-01-05 17:28:26.398 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_build_uint2_array(smallint) while casting return value to function's return type
2025-01-05 17:28:26.398 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: select test_build_uint2_array(-1::int2);
2025-01-05 17:28:26.399 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check"
2025-01-05 17:28:26.399 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_domain_array(integer[]) line 3 at RETURN
2025-01-05 17:28:26.399 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: select test_argresult_domain_array(array[4,2]);
2025-01-05 17:28:26.401 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check"
2025-01-05 17:28:26.401 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: select test_argresult_domain_array2(array[4,2]);
2025-01-05 17:28:26.405 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.405 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_result_nnint_container(integer,integer) line 3 at RETURN
2025-01-05 17:28:26.405 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT test_result_nnint_container(3, null);
2025-01-05 17:28:26.406 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.406 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint_container(integer,integer,integer) line 4 at assignment
2025-01-05 17:28:26.406 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint_container(1,2,null);
2025-01-05 17:28:26.407 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.407 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint_container(integer,integer,integer) line 2 during statement block local variable initialization
2025-01-05 17:28:26.407 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint_container(1,null,3);
2025-01-05 17:28:26.408 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values
2025-01-05 17:28:26.408 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint_container2(integer,integer,integer) line 4 at assignment
2025-01-05 17:28:26.408 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint_container2(1,2,null);
2025-01-05 17:28:26.410 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check"
2025-01-05 17:28:26.410 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT read_ordered_named_pair(row(2, 1));
2025-01-05 17:28:26.411 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check"
2025-01-05 17:28:26.411 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function build_ordered_named_pair(integer,integer) while casting return value to function's return type
2025-01-05 17:28:26.411 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT build_ordered_named_pair(2,1);
2025-01-05 17:28:26.413 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check"
2025-01-05 17:28:26.413 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_named_pair(integer,integer,integer) line 4 at assignment
2025-01-05 17:28:26.413 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_named_pair(1,2,0);
2025-01-05 17:28:26.413 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check"
2025-01-05 17:28:26.413 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_named_pair(integer,integer,integer) line 2 during statement block local variable initialization
2025-01-05 17:28:26.413 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_named_pair(2,1,3);
2025-01-05 17:28:26.414 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check"
2025-01-05 17:28:26.414 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function build_ordered_named_pairs(integer,integer) while casting return value to function's return type
2025-01-05 17:28:26.414 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT build_ordered_named_pairs(2,1);
2025-01-05 17:28:26.415 GMT client backend[6672] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check"
2025-01-05 17:28:26.415 GMT client backend[6672] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_named_pairs(integer,integer,integer) line 2 during statement block local variable initialization
2025-01-05 17:28:26.415 GMT client backend[6672] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_named_pairs(2,1,3);
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: variable "foo" does not exist
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo%type; begin end $$;
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: variable "notice" does not exist
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x notice%type; begin end $$;
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: relation "foo" does not exist
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.540 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar%type; begin end $$;
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: schema "foo" does not exist
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar.baz%type; begin end $$;
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: relation "public.foo" does not exist
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x public.foo.bar%type; begin end $$;
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: column "zed" of relation "misc_table" does not exist
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x public.misc_table.zed%type; begin end $$;
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: relation "foo" does not exist
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo%rowtype; begin end $$;
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: relation "notice" does not exist
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x notice%rowtype; begin end $$;
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: schema "foo" does not exist
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar%rowtype; begin end $$;
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: cross-database references are not implemented: "foo.bar.baz"
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.541 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar.baz%rowtype; begin end $$;
2025-01-05 17:28:26.542 GMT client backend[3320] pg_regress/plpgsql_misc ERROR: relation "public.foo" does not exist
2025-01-05 17:28:26.542 GMT client backend[3320] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1
2025-01-05 17:28:26.542 GMT client backend[3320] pg_regress/plpgsql_misc STATEMENT: do $$ declare x public.foo%rowtype; begin end $$;
2025-01-05 17:28:26.657 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.657 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column 1.
2025-01-05 17:28:26.657 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type
2025-01-05 17:28:26.657 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select retc(42);
2025-01-05 17:28:26.658 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.658 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Number of returned columns (3) does not match expected column count (2).
2025-01-05 17:28:26.658 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type
2025-01-05 17:28:26.658 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select retc(42);
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column 1.
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select retc(42);
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Number of returned columns (3) does not match expected column count (2).
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type
2025-01-05 17:28:26.660 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select retc(42);
2025-01-05 17:28:26.665 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "c" has no field "x"
2025-01-05 17:28:26.665 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "c.x = 1"
PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.665 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ declare c two_int8s; begin c.x = 1; end $$;
2025-01-05 17:28:26.665 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "c" has no field "x"
2025-01-05 17:28:26.665 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "c.x = 1"
PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.665 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin c.x = 1; end $$;
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "c" has no field "x"
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "c.x.q1 = 1"
PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin c.x.q1 = 1; end $$;
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record ERROR: cannot assign to field "x" of column "c" because there is no such column in data type two_int8s at character 1
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record QUERY: c.c2.x = 1
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin c.c2.x = 1; end $$;
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record ERROR: "d.c2.x" is not a known variable at character 37
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin d.c2.x = 1; end $$;
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "c" has no field "x"
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "b.c.x = 1"
PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ <<b>> declare c two_int8s; begin b.c.x = 1; end $$;
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "c" has no field "x"
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "b.c.x = 1"
PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ <<b>> declare c nested_int8s; begin b.c.x = 1; end $$;
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "c" has no field "x"
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "b.c.x.q1 = 1"
PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.666 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ <<b>> declare c nested_int8s; begin b.c.x.q1 = 1; end $$;
2025-01-05 17:28:26.667 GMT client backend[4564] pg_regress/plpgsql_record ERROR: cannot assign to field "x" of column "b" because there is no such column in data type two_int8s at character 1
2025-01-05 17:28:26.667 GMT client backend[4564] pg_regress/plpgsql_record QUERY: b.c.c2.x = 1
2025-01-05 17:28:26.667 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 1 at assignment
2025-01-05 17:28:26.667 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ <<b>> declare c nested_int8s; begin b.c.c2.x = 1; end $$;
2025-01-05 17:28:26.667 GMT client backend[4564] pg_regress/plpgsql_record ERROR: "b.d.c2" is not a known variable at character 43
2025-01-05 17:28:26.667 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$ <<b>> declare c nested_int8s; begin b.d.c2.x = 1; end $$;
2025-01-05 17:28:26.672 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "r1" has no field "nosuchfield"
2025-01-05 17:28:26.672 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "r1.nosuchfield"
PL/pgSQL function inline_code_block line 7 at RAISE
2025-01-05 17:28:26.672 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r1 two_int8s;
begin
raise notice 'r1.q1 = %', r1.q1;
raise notice 'r1.q2 = %', r1.q2;
raise notice 'r1 = %', r1;
raise notice 'r1.nosuchfield = %', r1.nosuchfield;
end$$;
2025-01-05 17:28:26.672 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "r1" is not assigned yet
2025-01-05 17:28:26.672 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: The tuple structure of a not-yet-assigned record is indeterminate.
2025-01-05 17:28:26.672 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "r1.f1"
PL/pgSQL function inline_code_block line 5 at RAISE
2025-01-05 17:28:26.672 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r1 record;
begin
raise notice 'r1 = %', r1;
raise notice 'r1.f1 = %', r1.f1;
raise notice 'r1.f2 = %', r1.f2;
raise notice 'r1 = %', r1;
end$$;
2025-01-05 17:28:26.673 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "r1" has no field "nosuchfield"
2025-01-05 17:28:26.673 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "r1.nosuchfield"
PL/pgSQL function inline_code_block line 9 at RAISE
2025-01-05 17:28:26.673 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r1 record;
begin
raise notice 'r1 = %', r1;
r1 := row(1,2);
raise notice 'r1.f1 = %', r1.f1;
raise notice 'r1.f2 = %', r1.f2;
raise notice 'r1 = %', r1;
raise notice 'r1.nosuchfield = %', r1.nosuchfield;
end$$;
2025-01-05 17:28:26.674 GMT client backend[4564] pg_regress/plpgsql_record ERROR: variable "r1" has pseudo-type record[]
2025-01-05 17:28:26.674 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 2
2025-01-05 17:28:26.674 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r1 record[];
begin
end$$;
2025-01-05 17:28:26.674 GMT client backend[4564] pg_regress/plpgsql_record ERROR: variable "r2" has pseudo-type record[]
2025-01-05 17:28:26.674 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 3
2025-01-05 17:28:26.674 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r1 record;
r2 r1%type[];
begin
end$$;
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3).
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int);
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column 2.
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.682 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint);
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3).
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int);
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column 2.
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.683 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint);
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3).
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int);
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column 2.
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.687 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint);
2025-01-05 17:28:26.688 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.688 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3).
2025-01-05 17:28:26.688 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.688 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int);
2025-01-05 17:28:26.689 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.689 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column 2.
2025-01-05 17:28:26.689 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type
2025-01-05 17:28:26.689 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint);
2025-01-05 17:28:26.689 GMT client backend[4564] pg_regress/plpgsql_record ERROR: function getf1(integer) does not exist at character 8
2025-01-05 17:28:26.689 GMT client backend[4564] pg_regress/plpgsql_record HINT: No function matches the given name and argument types. You might need to add explicit type casts.
2025-01-05 17:28:26.689 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select getf1(1);
2025-01-05 17:28:26.691 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "x" has no field "f1"
2025-01-05 17:28:26.691 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "x.f1"
PL/pgSQL function getf1(record) line 1 at RETURN
2025-01-05 17:28:26.691 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select getf1(row(1,2)::two_int8s);
2025-01-05 17:28:26.692 GMT client backend[4564] pg_regress/plpgsql_record ERROR: could not identify column "f2" in record data type at character 1
2025-01-05 17:28:26.692 GMT client backend[4564] pg_regress/plpgsql_record QUERY: $1.f2
2025-01-05 17:28:26.692 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function getf2(record) line 1 at RETURN
2025-01-05 17:28:26.692 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select getf2(row(1,2));
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "r" is not assigned yet
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: The tuple structure of a not-yet-assigned record is indeterminate.
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnssetofholes() line 4 at RETURN NEXT
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select returnssetofholes();
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record DETAIL: Number of returned columns (3) does not match expected column count (2).
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnssetofholes() line 3 at RETURN NEXT
2025-01-05 17:28:26.695 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select returnssetofholes();
2025-01-05 17:28:26.701 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "r" has no field "f1"
2025-01-05 17:28:26.701 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function sillyaddone(integer) line 1 at assignment
2025-01-05 17:28:26.701 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select sillyaddone(42);
2025-01-05 17:28:26.701 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "x" has no field "f3"
2025-01-05 17:28:26.701 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "x.f3"
PL/pgSQL function getf3(mutable) line 1 at RETURN
2025-01-05 17:28:26.701 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select getf3(null::mutable);
2025-01-05 17:28:26.703 GMT client backend[4564] pg_regress/plpgsql_record ERROR: record "x" has no field "f3"
2025-01-05 17:28:26.703 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function getf3(mutable) line 1 at RETURN
2025-01-05 17:28:26.703 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select getf3(null::mutable);
2025-01-05 17:28:26.704 GMT client backend[4564] pg_regress/plpgsql_record ERROR: type "mutable2" does not exist at character 12
2025-01-05 17:28:26.704 GMT client backend[4564] pg_regress/plpgsql_record QUERY: declare r mutable2; begin r.f1 := $1; return r.f1 + 2; end
2025-01-05 17:28:26.704 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: compilation of PL/pgSQL function "sillyaddtwo" near line 1
2025-01-05 17:28:26.704 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select sillyaddtwo(42);
2025-01-05 17:28:26.710 GMT client backend[4564] pg_regress/plpgsql_record ERROR: type "mutable2" does not exist
2025-01-05 17:28:26.710 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function sillyaddtwo(integer) line 1 at assignment
2025-01-05 17:28:26.710 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select sillyaddtwo(42);
2025-01-05 17:28:26.722 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.722 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select read_ordered_int8s(row(2, 1));
2025-01-05 17:28:26.723 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.723 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s(bigint,bigint) while casting return value to function's return type
2025-01-05 17:28:26.723 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s(2,1);
2025-01-05 17:28:26.724 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.724 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_2(bigint,bigint) while casting return value to function's return type
2025-01-05 17:28:26.724 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_2(2,1);
2025-01-05 17:28:26.725 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.725 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_3(bigint,bigint) while casting return value to function's return type
2025-01-05 17:28:26.725 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_3(2,1);
2025-01-05 17:28:26.727 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.727 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_4(bigint,bigint) line 2 at assignment
2025-01-05 17:28:26.727 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_4(2,1);
2025-01-05 17:28:26.728 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.728 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_a(bigint,bigint) while casting return value to function's return type
2025-01-05 17:28:26.728 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_a(2,1);
2025-01-05 17:28:26.728 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.728 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment
2025-01-05 17:28:26.728 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r ordered_int8s;
begin
r.q1 := null;
r.q2 := 43;
r.q1 := 42;
r.q2 := 41; -- fail
end$$;
2025-01-05 17:28:26.729 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.729 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment
2025-01-05 17:28:26.729 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r ordered_int8s;
begin
r := null;
r := row(null,null);
r := row(1,2);
r := row(2,1); -- fail
end$$;
2025-01-05 17:28:26.729 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check"
2025-01-05 17:28:26.729 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 4 at FOR over SELECT rows
2025-01-05 17:28:26.729 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r ordered_int8s;
begin
for r in values (1,2),(3,4),(6,5) loop
raise notice 'r = %', r;
end loop;
end$$;
2025-01-05 17:28:26.757 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_texts violates check constraint "ordered_texts_check"
2025-01-05 17:28:26.757 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 4 at FOR over SELECT rows
2025-01-05 17:28:26.757 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare d ordered_texts;
begin
for d in select a, b from sometable loop
raise notice 'succeeded at "%"', d.f1;
end loop;
end$$;
2025-01-05 17:28:26.762 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_texts violates check constraint "ordered_texts_check"
2025-01-05 17:28:26.762 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 6 at assignment
2025-01-05 17:28:26.762 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r record; d ordered_texts;
begin
for r in select * from sometable loop
raise notice 'processing row %', r.id;
d := row(r.a, r.b);
end loop;
end$$;
2025-01-05 17:28:26.767 GMT client backend[4564] pg_regress/plpgsql_record ERROR: value for domain ordered_texts violates check constraint "ordered_texts_check"
2025-01-05 17:28:26.767 GMT client backend[4564] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 8 at assignment
2025-01-05 17:28:26.767 GMT client backend[4564] pg_regress/plpgsql_record STATEMENT: do $$
declare r record; d ordered_texts;
begin
for r in select * from sometable loop
raise notice 'processing row %', r.id;
d := null;
d.f1 := r.a;
d.f2 := r.b;
end loop;
end$$;
2025-01-05 17:28:26.921 GMT client backend[6464] pg_regress/plpgsql_simple ERROR: division by zero
2025-01-05 17:28:26.921 GMT client backend[6464] pg_regress/plpgsql_simple CONTEXT: SQL function "simplesql" during inlining
SQL statement "select simplesql()"
PL/pgSQL function simplecaller() line 4 at SQL statement
2025-01-05 17:28:26.921 GMT client backend[6464] pg_regress/plpgsql_simple STATEMENT: select simplecaller();
2025-01-05 17:28:27.081 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.081 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test1(integer,text) line 6 at COMMIT
2025-01-05 17:28:27.081 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test1(9, 'error');
2025-01-05 17:28:27.081 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.081 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 1 at COMMIT
2025-01-05 17:28:27.081 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN COMMIT; END $$;
2025-01-05 17:28:27.087 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.087 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test2() line 6 at COMMIT
2025-01-05 17:28:27.087 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: SELECT transaction_test2();
2025-01-05 17:28:27.088 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.088 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test1(integer,text) line 6 at COMMIT
SQL statement "CALL transaction_test1(9, 'error')"
PL/pgSQL function transaction_test3() line 3 at CALL
2025-01-05 17:28:27.088 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: SELECT transaction_test3();
2025-01-05 17:28:27.090 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.090 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 1 at COMMIT
SQL statement "DO LANGUAGE plpgsql $x$ BEGIN COMMIT; END $x$"
PL/pgSQL function transaction_test4() line 3 at EXECUTE
2025-01-05 17:28:27.090 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: SELECT transaction_test4();
2025-01-05 17:28:27.091 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.091 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test5() line 3 at COMMIT
2025-01-05 17:28:27.091 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test5();
2025-01-05 17:28:27.092 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.092 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test5b() line 3 at COMMIT
2025-01-05 17:28:27.092 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test5b();
2025-01-05 17:28:27.118 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: invalid transaction termination
2025-01-05 17:28:27.118 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test1(integer,text) line 6 at COMMIT
SQL statement "CALL transaction_test1(10, $x$baz$x$)"
PL/pgSQL function transaction_test8() line 3 at EXECUTE
2025-01-05 17:28:27.118 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test8();
2025-01-05 17:28:27.172 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: division by zero
2025-01-05 17:28:27.172 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: SQL statement "INSERT INTO test1 (a) VALUES (12/(r.x-2))"
PL/pgSQL function inline_code_block line 6 at SQL statement
2025-01-05 17:28:27.172 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
DECLARE
r RECORD;
BEGIN
FOR r IN SELECT * FROM test2 ORDER BY x LOOP
INSERT INTO test1 (a) VALUES (12/(r.x-2));
COMMIT;
END LOOP;
END;
$$;
2025-01-05 17:28:27.189 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: cannot perform transaction commands inside a cursor loop that is not read-only
2025-01-05 17:28:27.189 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 7 at ROLLBACK
2025-01-05 17:28:27.189 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
DECLARE
r RECORD;
BEGIN
FOR r IN UPDATE test2 SET x = x * 2 RETURNING x LOOP
INSERT INTO test1 (a) VALUES (r.x);
ROLLBACK;
END LOOP;
END;
$$;
2025-01-05 17:28:27.205 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: cannot commit while a subtransaction is active
2025-01-05 17:28:27.205 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 5 at COMMIT
2025-01-05 17:28:27.205 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
BEGIN
INSERT INTO test1 (a) VALUES (1);
COMMIT;
INSERT INTO test1 (a) VALUES (1/0);
COMMIT;
EXCEPTION
WHEN division_by_zero THEN
RAISE NOTICE 'caught division_by_zero';
END;
END;
$$;
2025-01-05 17:28:27.209 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: cannot roll back while a subtransaction is active
2025-01-05 17:28:27.209 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 5 at ROLLBACK
2025-01-05 17:28:27.209 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
BEGIN
INSERT INTO test1 (a) VALUES (1);
ROLLBACK;
INSERT INTO test1 (a) VALUES (1/0);
ROLLBACK;
EXCEPTION
WHEN division_by_zero THEN
RAISE NOTICE 'caught division_by_zero';
END;
END;
$$;
2025-01-05 17:28:27.226 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: duplicate key value violates unique constraint "test3_y_key"
2025-01-05 17:28:27.226 GMT client backend[1300] pg_regress/plpgsql_transaction DETAIL: Key (y)=(1) already exists.
2025-01-05 17:28:27.226 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 9 at COMMIT
2025-01-05 17:28:27.226 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
CREATE TABLE test3 (y int UNIQUE DEFERRABLE INITIALLY DEFERRED);
COMMIT;
INSERT INTO test3 (y) VALUES (1);
COMMIT;
INSERT INTO test3 (y) VALUES (1);
INSERT INTO test3 (y) VALUES (2);
COMMIT;
INSERT INTO test3 (y) VALUES (3); -- won't get here
END;
$$;
2025-01-05 17:28:27.232 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: division by zero
2025-01-05 17:28:27.232 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function cursor_fail_during_commit() line 6 at COMMIT
2025-01-05 17:28:27.232 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: CALL cursor_fail_during_commit();
2025-01-05 17:28:27.237 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: division by zero
2025-01-05 17:28:27.237 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function cursor_fail_during_rollback() line 6 at ROLLBACK
2025-01-05 17:28:27.237 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: CALL cursor_fail_during_rollback();
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: SQL statement "SET TRANSACTION ISOLATION LEVEL REPEATABLE READ"
PL/pgSQL function inline_code_block line 3 at SQL statement
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
END;
$$;
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: unsupported transaction command in PL/pgSQL
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 3 at SQL statement
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
SAVEPOINT foo;
END;
$$;
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction ERROR: EXECUTE of transaction commands is not implemented
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 3 at EXECUTE
2025-01-05 17:28:27.239 GMT client backend[1300] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$
BEGIN
EXECUTE 'COMMIT';
END;
$$;
2025-01-05 17:28:27.507 GMT client backend[1796] pg_regress/plpgsql_trap ERROR: -100 is less than zero
2025-01-05 17:28:27.507 GMT client backend[1796] pg_regress/plpgsql_trap CONTEXT: PL/pgSQL function trap_zero_divide(integer) line 12 at RAISE
2025-01-05 17:28:27.507 GMT client backend[1796] pg_regress/plpgsql_trap STATEMENT: select trap_zero_divide(-100);
2025-01-05 17:28:28.582 GMT client backend[1796] pg_regress/plpgsql_trap LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp1796.0", size 72228864
2025-01-05 17:28:28.582 GMT client backend[1796] pg_regress/plpgsql_trap CONTEXT: PL/pgSQL function trap_timeout() line 6 during exception cleanup
2025-01-05 17:28:28.582 GMT client backend[1796] pg_regress/plpgsql_trap STATEMENT: select trap_timeout();
2025-01-05 17:28:28.583 GMT client backend[1796] pg_regress/plpgsql_trap ERROR: end of function
2025-01-05 17:28:28.583 GMT client backend[1796] pg_regress/plpgsql_trap CONTEXT: PL/pgSQL function trap_timeout() line 15 at RAISE
2025-01-05 17:28:28.583 GMT client backend[1796] pg_regress/plpgsql_trap STATEMENT: select trap_timeout();
2025-01-05 17:28:28.598 GMT client backend[1796] pg_regress/plpgsql_trap ERROR: insert or update on table "leaf" violates foreign key constraint "leaf_f1_fkey"
2025-01-05 17:28:28.598 GMT client backend[1796] pg_regress/plpgsql_trap DETAIL: Key (f1)=(2) is not present in table "root".
2025-01-05 17:28:28.598 GMT client backend[1796] pg_regress/plpgsql_trap STATEMENT: insert into leaf values(2);
2025-01-05 17:28:28.607 GMT client backend[1796] pg_regress/plpgsql_trap ERROR: insert or update on table "leaf" violates foreign key constraint "leaf_f1_fkey"
2025-01-05 17:28:28.607 GMT client backend[1796] pg_regress/plpgsql_trap DETAIL: Key (f1)=(2) is not present in table "root".
2025-01-05 17:28:28.607 GMT client backend[1796] pg_regress/plpgsql_trap STATEMENT: set constraints all immediate;
2025-01-05 17:28:28.608 GMT client backend[1796] pg_regress/plpgsql_trap ERROR: insert or update on table "leaf" violates foreign key constraint "leaf_f1_fkey"
2025-01-05 17:28:28.608 GMT client backend[1796] pg_regress/plpgsql_trap DETAIL: Key (f1)=(2) is not present in table "root".
2025-01-05 17:28:28.608 GMT client backend[1796] pg_regress/plpgsql_trap STATEMENT: commit;
2025-01-05 17:28:28.929 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 39
2025-01-05 17:28:28.929 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x constant int;
begin
x := 42; -- fail
end$$;
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 50
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x constant int; y int;
begin
for x, y in select 1, 2 loop -- fail
end loop;
end$$;
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 41
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x constant int[];
begin
x[1] := 42; -- fail
end$$;
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: syntax error at or near "[" at character 53
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x constant int[]; y int;
begin
for x[1], y in select 1, 2 loop -- fail (currently, unsupported syntax)
end loop;
end$$;
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 46
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x constant var_record;
begin
x.f1 := 42; -- fail
end$$;
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 57
2025-01-05 17:28:28.930 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x constant var_record; y int;
begin
for x.f1, y in select 1, 2 loop -- fail
end loop;
end$$;
2025-01-05 17:28:28.931 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: division by zero
2025-01-05 17:28:28.931 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL expression "1/0"
PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.931 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x int := 1/0; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.932 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" must have a default value, since it's declared NOT NULL at character 21
2025-01-05 17:28:28.932 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x int not null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x int not null := 42;
begin
raise notice 'x = %', x;
x := null; -- fail
end$$;
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x int not null := null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" must have a default value, since it's declared NOT NULL at character 24
2025-01-05 17:28:28.933 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x record not null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x record not null := row(42);
begin
raise notice 'x = %', x;
x := row(null); -- ok
raise notice 'x = %', x;
x := null; -- fail
end$$;
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x record not null := null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: variable "x" must have a default value, since it's declared NOT NULL at character 28
2025-01-05 17:28:28.934 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record not null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.935 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL
2025-01-05 17:28:28.935 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment
2025-01-05 17:28:28.935 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record not null := row(41,42);
begin
raise notice 'x = %', x;
x := row(null,null); -- ok
raise notice 'x = %', x;
x := null; -- fail
end$$;
2025-01-05 17:28:28.935 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL
2025-01-05 17:28:28.935 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.935 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record not null := null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.936 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: domain int_nn does not allow null values
2025-01-05 17:28:28.936 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.936 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x int_nn; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.936 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: domain int_nn does not allow null values
2025-01-05 17:28:28.936 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.936 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x int_nn := null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: domain int_nn does not allow null values
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x int_nn := 42;
begin
raise notice 'x = %', x;
x := null; -- fail
end$$;
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: domain var_record_nn does not allow null values
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_nn; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: domain var_record_nn does not allow null values
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.937 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_nn := null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: domain var_record_nn does not allow null values
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 6 at assignment
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_nn := row(1,2);
begin
raise notice 'x = %', x;
x := row(null,null); -- ok
x := null; -- fail
end$$;
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check"
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_colnn; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check"
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.938 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_colnn := null; -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.939 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check"
2025-01-05 17:28:28.939 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-01-05 17:28:28.939 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_colnn := row(1,null); -- fail
begin
raise notice 'x = %', x;
end$$;
2025-01-05 17:28:28.939 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check"
2025-01-05 17:28:28.939 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment
2025-01-05 17:28:28.939 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_colnn := row(1,2);
begin
raise notice 'x = %', x;
x := null; -- fail
end$$;
2025-01-05 17:28:28.940 GMT client backend[6564] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check"
2025-01-05 17:28:28.940 GMT client backend[6564] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment
2025-01-05 17:28:28.940 GMT client backend[6564] pg_regress/plpgsql_varprops STATEMENT: do $$
declare x var_record_colnn := row(1,2);
begin
raise notice 'x = %', x;
x := row(null,null); -- fail
end$$;
2025-01-05 17:28:29.014 GMT postmaster[6752] LOG: received fast shutdown request
2025-01-05 17:28:29.014 GMT postmaster[6752] LOG: aborting any active transactions
TRAP: failed Assert("(remainMask.mask | targetMask.mask) == BTYPE_MASK_ALL.mask"), File: "../src/backend/postmaster/postmaster.c", Line: 2896, PID: 6752
abort() has been called