2025-01-05 17:28:31.229 GMT postmaster[1228] LOG: starting PostgreSQL 18devel on x86_64-windows, compiled by msvc-19.29.30157, 64-bit 2025-01-05 17:28:31.233 GMT postmaster[1228] LOG: listening on Unix socket "c:/cirrus/.s.PGSQL.40002" 2025-01-05 17:28:31.259 GMT startup[5600] LOG: database system was shut down at 2025-01-05 17:25:50 GMT 2025-01-05 17:28:31.285 GMT client backend[6020] [unknown] FATAL: the database system is starting up 2025-01-05 17:28:31.356 GMT postmaster[1228] LOG: database system is ready to accept connections 2025-01-05 17:28:31.419 GMT client backend[6956] [unknown] FATAL: the database system is starting up 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test LOG: log 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test CONTEXT: PL/Python function "elog_test_basic" 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test STATEMENT: SELECT elog_test_basic(); 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test WARNING: warning 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test CONTEXT: PL/Python function "elog_test_basic" 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test ERROR: plpy.Error: error 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test CONTEXT: Traceback (most recent call last): PL/Python function "elog_test_basic", line 10, in plpy.error('error') PL/Python function "elog_test_basic" 2025-01-05 17:28:32.838 GMT client backend[6616] pg_regress/plpython_test STATEMENT: SELECT elog_test_basic(); 2025-01-05 17:28:33.042 GMT client backend[3936] pg_regress/plpython_do ERROR: Exception: error test 2025-01-05 17:28:33.042 GMT client backend[3936] pg_regress/plpython_do CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in raise Exception("error test") PL/Python anonymous code block 2025-01-05 17:28:33.042 GMT client backend[3936] pg_regress/plpython_do STATEMENT: DO $$ raise Exception("error test") $$ LANGUAGE plpython3u; 2025-01-05 17:28:33.779 GMT client backend[5964] pg_regress/plpython_spi ERROR: plpy.Error: command did not produce a result set 2025-01-05 17:28:33.779 GMT client backend[5964] pg_regress/plpython_spi CONTEXT: Traceback (most recent call last): PL/Python function "result_metadata_test", line 6, in plpy.info(result.colnames()) PL/Python function "result_metadata_test" 2025-01-05 17:28:33.779 GMT client backend[5964] pg_regress/plpython_spi STATEMENT: SELECT result_metadata_test($$CREATE TEMPORARY TABLE foo1 (a int, b text)$$); 2025-01-05 17:28:33.809 GMT client backend[5964] pg_regress/plpython_spi ERROR: TypeError: Expected sequence of 1 argument, got 2: ['a', 'b'] 2025-01-05 17:28:33.809 GMT client backend[5964] pg_regress/plpython_spi CONTEXT: Traceback (most recent call last): PL/Python function "cursor_plan_wrong_args", line 4, in c = plpy.cursor(plan, ["a", "b"]) PL/Python function "cursor_plan_wrong_args" 2025-01-05 17:28:33.809 GMT client backend[5964] pg_regress/plpython_spi STATEMENT: SELECT cursor_plan_wrong_args(); 2025-01-05 17:28:34.214 GMT client backend[6520] pg_regress/plpython_void ERROR: PL/Python function with return type "void" did not return None 2025-01-05 17:28:34.214 GMT client backend[6520] pg_regress/plpython_void CONTEXT: while creating return value PL/Python function "test_void_func2" 2025-01-05 17:28:34.214 GMT client backend[6520] pg_regress/plpython_void STATEMENT: SELECT test_void_func2(); 2025-01-05 17:28:34.321 GMT client backend[3992] pg_regress/plpython_call ERROR: PL/Python procedure did not return None 2025-01-05 17:28:34.321 GMT client backend[3992] pg_regress/plpython_call CONTEXT: PL/Python procedure "test_proc2" 2025-01-05 17:28:34.321 GMT client backend[3992] pg_regress/plpython_call STATEMENT: CALL test_proc2(); 2025-01-05 17:28:35.370 GMT client backend[6284] pg_regress/plpython_setof ERROR: returned object cannot be iterated 2025-01-05 17:28:35.370 GMT client backend[6284] pg_regress/plpython_setof DETAIL: PL/Python set-returning functions must return an iterable object. 2025-01-05 17:28:35.370 GMT client backend[6284] pg_regress/plpython_setof CONTEXT: PL/Python function "test_setof_error" 2025-01-05 17:28:35.370 GMT client backend[6284] pg_regress/plpython_setof STATEMENT: SELECT test_setof_error(); 2025-01-05 17:28:36.794 GMT client backend[4216] pg_regress/plpython_record ERROR: key "second" not found in mapping 2025-01-05 17:28:36.794 GMT client backend[4216] pg_regress/plpython_record HINT: To return null in a column, add the value None to the mapping with the key named after the column. 2025-01-05 17:28:36.794 GMT client backend[4216] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error1" 2025-01-05 17:28:36.794 GMT client backend[4216] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error1(); 2025-01-05 17:28:36.795 GMT client backend[4216] pg_regress/plpython_record ERROR: length of returned sequence did not match number of columns in row 2025-01-05 17:28:36.795 GMT client backend[4216] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error2" 2025-01-05 17:28:36.795 GMT client backend[4216] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error2(); 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record ERROR: attribute "second" does not exist in Python object 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record HINT: To return null in a column, let the returned object have an attribute named after column with value None. 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error3" 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error3(); 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record ERROR: malformed record literal: "foo" 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record DETAIL: Missing left parenthesis. 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error4" 2025-01-05 17:28:36.796 GMT client backend[4216] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error4(); 2025-01-05 17:28:37.548 GMT client backend[5836] pg_regress/plpython_trigger ERROR: unexpected return value from trigger procedure 2025-01-05 17:28:37.548 GMT client backend[5836] pg_regress/plpython_trigger DETAIL: Expected None or a string. 2025-01-05 17:28:37.548 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid1" 2025-01-05 17:28:37.548 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: INSERT INTO trigger_test VALUES (1, 'one'); 2025-01-05 17:28:37.550 GMT client backend[5836] pg_regress/plpython_trigger WARNING: PL/Python trigger function returned "MODIFY" in a DELETE trigger -- ignored 2025-01-05 17:28:37.550 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid2" 2025-01-05 17:28:37.552 GMT client backend[5836] pg_regress/plpython_trigger ERROR: unexpected return value from trigger procedure 2025-01-05 17:28:37.552 GMT client backend[5836] pg_regress/plpython_trigger DETAIL: Expected None, "OK", "SKIP", or "MODIFY". 2025-01-05 17:28:37.552 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid3" 2025-01-05 17:28:37.552 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-01-05 17:28:37.554 GMT client backend[5836] pg_regress/plpython_trigger ERROR: unexpected return value from trigger procedure 2025-01-05 17:28:37.554 GMT client backend[5836] pg_regress/plpython_trigger DETAIL: Expected None, "OK", "SKIP", or "MODIFY". 2025-01-05 17:28:37.554 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid3u" 2025-01-05 17:28:37.554 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-01-05 17:28:37.555 GMT client backend[5836] pg_regress/plpython_trigger ERROR: TD["new"] deleted, cannot modify row 2025-01-05 17:28:37.555 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid4" 2025-01-05 17:28:37.555 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-01-05 17:28:37.557 GMT client backend[5836] pg_regress/plpython_trigger ERROR: TD["new"] is not a dictionary 2025-01-05 17:28:37.557 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid5" 2025-01-05 17:28:37.557 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-01-05 17:28:37.559 GMT client backend[5836] pg_regress/plpython_trigger ERROR: TD["new"] dictionary key at ordinal position 0 is not a string 2025-01-05 17:28:37.559 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid6" 2025-01-05 17:28:37.559 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-01-05 17:28:37.561 GMT client backend[5836] pg_regress/plpython_trigger ERROR: key "a" found in TD["new"] does not exist as a column in the triggering row 2025-01-05 17:28:37.561 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid7" 2025-01-05 17:28:37.561 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-01-05 17:28:37.562 GMT client backend[5836] pg_regress/plpython_trigger ERROR: key "a" found in TD["new"] does not exist as a column in the triggering row 2025-01-05 17:28:37.562 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid7u" 2025-01-05 17:28:37.562 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-01-05 17:28:37.563 GMT client backend[5836] pg_regress/plpython_trigger ERROR: trigger functions can only be called as triggers 2025-01-05 17:28:37.563 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: SELECT stupid7(); 2025-01-05 17:28:37.622 GMT client backend[5836] pg_regress/plpython_trigger ERROR: cannot set generated column "j" 2025-01-05 17:28:37.622 GMT client backend[5836] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "generated_test_func1" 2025-01-05 17:28:37.622 GMT client backend[5836] pg_regress/plpython_trigger STATEMENT: INSERT INTO trigger_test_generated (i) VALUES (1); 2025-01-05 17:28:38.008 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-01-05 17:28:38.008 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_booltrue(false, true); 2025-01-05 17:28:38.009 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-01-05 17:28:38.009 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_booltrue" 2025-01-05 17:28:38.009 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_booltrue(true, false); 2025-01-05 17:28:38.011 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-01-05 17:28:38.011 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_uint2" 2025-01-05 17:28:38.011 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_uint2(100::uint2, -50); 2025-01-05 17:28:38.013 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain nnint violates check constraint "nnint_check" 2025-01-05 17:28:38.013 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_nnint(null, 20); 2025-01-05 17:28:38.013 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain nnint violates check constraint "nnint_check" 2025-01-05 17:28:38.013 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_nnint" 2025-01-05 17:28:38.013 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_nnint(10, null); 2025-01-05 17:28:38.015 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-01-05 17:28:38.015 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10('hello world', 'hello wold'); 2025-01-05 17:28:38.015 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-01-05 17:28:38.015 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_bytea10" 2025-01-05 17:28:38.015 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10('hello word', 'hello world'); 2025-01-05 17:28:38.016 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-01-05 17:28:38.016 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10(null, 'hello word'); 2025-01-05 17:28:38.016 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-01-05 17:28:38.016 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_bytea10" 2025-01-05 17:28:38.016 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10('hello word', null); 2025-01-05 17:28:38.032 GMT client backend[4984] pg_regress/plpython_types ERROR: invalid input syntax for type integer: "abc" 2025-01-05 17:28:38.032 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_array_mixed2" 2025-01-05 17:28:38.032 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_array_mixed2(); 2025-01-05 17:28:38.043 GMT client backend[4984] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-01-05 17:28:38.043 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-01-05 17:28:38.043 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-01-05 17:28:38.044 GMT client backend[4984] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-01-05 17:28:38.044 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-01-05 17:28:38.044 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-01-05 17:28:38.045 GMT client backend[4984] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-01-05 17:28:38.045 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-01-05 17:28:38.045 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-01-05 17:28:38.046 GMT client backend[4984] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-01-05 17:28:38.046 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-01-05 17:28:38.046 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-01-05 17:28:38.047 GMT client backend[4984] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-01-05 17:28:38.047 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_malformed" 2025-01-05 17:28:38.047 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_malformed(); 2025-01-05 17:28:38.047 GMT client backend[4984] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-01-05 17:28:38.047 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_malformed2" 2025-01-05 17:28:38.047 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_malformed2(); 2025-01-05 17:28:38.048 GMT client backend[4984] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-01-05 17:28:38.048 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_malformed3" 2025-01-05 17:28:38.048 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_malformed3(); 2025-01-05 17:28:38.049 GMT client backend[4984] pg_regress/plpython_types ERROR: number of array dimensions exceeds the maximum allowed (6) 2025-01-05 17:28:38.049 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_toodeep" 2025-01-05 17:28:38.049 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_toodeep(); 2025-01-05 17:28:38.053 GMT client backend[4984] pg_regress/plpython_types ERROR: return value of function with array return type is not a Python sequence 2025-01-05 17:28:38.053 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_array_error" 2025-01-05 17:28:38.053 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_array_error(); 2025-01-05 17:28:38.057 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-01-05 17:28:38.057 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_array_domain_check_violation" 2025-01-05 17:28:38.057 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_array_domain_check_violation(); 2025-01-05 17:28:38.060 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-01-05 17:28:38.060 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_build_uint2_array" 2025-01-05 17:28:38.060 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_build_uint2_array(-1::int2); 2025-01-05 17:28:38.061 GMT client backend[4984] pg_regress/plpython_types ERROR: return value of function with array return type is not a Python sequence 2025-01-05 17:28:38.061 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_domain_array" 2025-01-05 17:28:38.061 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_type_conversion_domain_array(array[2,4]); 2025-01-05 17:28:38.061 GMT client backend[4984] pg_regress/plpython_types ERROR: return value of function with array return type is not a Python sequence 2025-01-05 17:28:38.061 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_domain_array" 2025-01-05 17:28:38.061 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_type_conversion_domain_array(array[4,2]); 2025-01-05 17:28:38.062 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-01-05 17:28:38.062 GMT client backend[4984] pg_regress/plpython_types STATEMENT: select test_type_conversion_domain_array2(array[4,2]); 2025-01-05 17:28:38.072 GMT client backend[4984] pg_regress/plpython_types ERROR: KeyError: 'bonus' 2025-01-05 17:28:38.072 GMT client backend[4984] pg_regress/plpython_types CONTEXT: Traceback (most recent call last): PL/Python function "test_composite_table_input", line 2, in return e['basesalary'] + e['bonus'] PL/Python function "test_composite_table_input" 2025-01-05 17:28:38.072 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT name, test_composite_table_input(employee.*) FROM employee; 2025-01-05 17:28:38.078 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain nnint violates check constraint "nnint_check" 2025-01-05 17:28:38.078 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "nnint_test" 2025-01-05 17:28:38.078 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT nnint_test(3, null); 2025-01-05 17:28:38.080 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-01-05 17:28:38.080 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT read_ordered_named_pair(row(2, 1)); 2025-01-05 17:28:38.081 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-01-05 17:28:38.081 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "build_ordered_named_pair" 2025-01-05 17:28:38.081 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT build_ordered_named_pair(2,1); 2025-01-05 17:28:38.082 GMT client backend[4984] pg_regress/plpython_types ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-01-05 17:28:38.082 GMT client backend[4984] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "build_ordered_named_pairs" 2025-01-05 17:28:38.082 GMT client backend[4984] pg_regress/plpython_types STATEMENT: SELECT build_ordered_named_pairs(2,1); 2025-01-05 17:28:38.532 GMT client backend[5892] pg_regress/plpython_error ERROR: could not compile PL/Python function "python_syntax_error" 2025-01-05 17:28:38.532 GMT client backend[5892] pg_regress/plpython_error DETAIL: SyntaxError: invalid syntax (, line 2) 2025-01-05 17:28:38.532 GMT client backend[5892] pg_regress/plpython_error STATEMENT: /* Flat out Python syntax error */ CREATE FUNCTION python_syntax_error() RETURNS text AS '.syntaxerror' LANGUAGE plpython3u; 2025-01-05 17:28:38.536 GMT client backend[5892] pg_regress/plpython_error ERROR: could not compile PL/Python function "python_syntax_error" 2025-01-05 17:28:38.536 GMT client backend[5892] pg_regress/plpython_error DETAIL: SyntaxError: invalid syntax (, line 2) 2025-01-05 17:28:38.536 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT python_syntax_error(); 2025-01-05 17:28:38.536 GMT client backend[5892] pg_regress/plpython_error ERROR: could not compile PL/Python function "python_syntax_error" 2025-01-05 17:28:38.536 GMT client backend[5892] pg_regress/plpython_error DETAIL: SyntaxError: invalid syntax (, line 2) 2025-01-05 17:28:38.536 GMT client backend[5892] pg_regress/plpython_error STATEMENT: /* Run the function twice to check if the hashtable entry gets cleaned up */ SELECT python_syntax_error(); 2025-01-05 17:28:38.537 GMT client backend[5892] pg_regress/plpython_error ERROR: spiexceptions.SyntaxError: syntax error at or near "syntax" at character 1 2025-01-05 17:28:38.537 GMT client backend[5892] pg_regress/plpython_error QUERY: syntax error 2025-01-05 17:28:38.537 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "sql_syntax_error", line 1, in plpy.execute("syntax error") PL/Python function "sql_syntax_error" 2025-01-05 17:28:38.537 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT sql_syntax_error(); 2025-01-05 17:28:38.538 GMT client backend[5892] pg_regress/plpython_error ERROR: IndexError: list index out of range 2025-01-05 17:28:38.538 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "exception_index_invalid", line 1, in return args[1] PL/Python function "exception_index_invalid" 2025-01-05 17:28:38.538 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT exception_index_invalid('test'); 2025-01-05 17:28:38.539 GMT client backend[5892] pg_regress/plpython_error ERROR: spiexceptions.UndefinedFunction: function test5(unknown) does not exist at character 8 2025-01-05 17:28:38.539 GMT client backend[5892] pg_regress/plpython_error HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-01-05 17:28:38.539 GMT client backend[5892] pg_regress/plpython_error QUERY: SELECT test5('foo') 2025-01-05 17:28:38.539 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "exception_index_invalid_nested", line 1, in rv = plpy.execute("SELECT test5('foo')") PL/Python function "exception_index_invalid_nested" 2025-01-05 17:28:38.539 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT exception_index_invalid_nested(); 2025-01-05 17:28:38.540 GMT client backend[5892] pg_regress/plpython_error ERROR: spiexceptions.UndefinedObject: type "test" does not exist 2025-01-05 17:28:38.540 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "invalid_type_uncaught", line 3, in SD["plan"] = plpy.prepare(q, [ "test" ]) PL/Python function "invalid_type_uncaught" 2025-01-05 17:28:38.540 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT invalid_type_uncaught('rick'); 2025-01-05 17:28:38.542 GMT client backend[5892] pg_regress/plpython_error ERROR: plpy.Error: type "test" does not exist 2025-01-05 17:28:38.542 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "invalid_type_reraised", line 6, in plpy.error(str(ex)) PL/Python function "invalid_type_reraised" 2025-01-05 17:28:38.542 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT invalid_type_reraised('rick'); 2025-01-05 17:28:38.546 GMT client backend[5892] pg_regress/plpython_error ERROR: plpy.Error: boom 2025-01-05 17:28:38.546 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "nested_error", line 10, in fun3() PL/Python function "nested_error", line 8, in fun3 fun2() PL/Python function "nested_error", line 5, in fun2 fun1() PL/Python function "nested_error", line 2, in fun1 plpy.error("boom") PL/Python function "nested_error" 2025-01-05 17:28:38.546 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT nested_error(); 2025-01-05 17:28:38.547 GMT client backend[5892] pg_regress/plpython_error ERROR: plpy.Error: boom 2025-01-05 17:28:38.547 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "nested_error_raise", line 10, in fun3() PL/Python function "nested_error_raise", line 8, in fun3 fun2() PL/Python function "nested_error_raise", line 5, in fun2 fun1() PL/Python function "nested_error_raise", line 2, in fun1 raise plpy.Error("boom") PL/Python function "nested_error_raise" 2025-01-05 17:28:38.547 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT nested_error_raise(); 2025-01-05 17:28:38.548 GMT client backend[5892] pg_regress/plpython_error WARNING: boom 2025-01-05 17:28:38.548 GMT client backend[5892] pg_regress/plpython_error CONTEXT: PL/Python function "nested_warning" 2025-01-05 17:28:38.549 GMT client backend[5892] pg_regress/plpython_error ERROR: AttributeError: module 'plpy' has no attribute 'nonexistent' 2025-01-05 17:28:38.549 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "toplevel_attribute_error", line 2, in plpy.nonexistent PL/Python function "toplevel_attribute_error" 2025-01-05 17:28:38.549 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT toplevel_attribute_error(); 2025-01-05 17:28:38.552 GMT client backend[5892] pg_regress/plpython_error ERROR: spiexceptions.DivisionByZero: division by zero 2025-01-05 17:28:38.552 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "python_traceback", line 11, in first() PL/Python function "python_traceback", line 3, in first second() PL/Python function "python_traceback", line 6, in second third() PL/Python function "python_traceback", line 9, in third plpy.execute("select sql_error()") PL/Python function "python_traceback" 2025-01-05 17:28:38.552 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT python_traceback(); 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error ERROR: division by zero 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error CONTEXT: SQL statement "select 1/0" PL/pgSQL function sql_error() line 3 at SQL statement 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT sql_error(); 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error ERROR: spiexceptions.DivisionByZero: division by zero 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "python_traceback", line 11, in first() PL/Python function "python_traceback", line 3, in first second() PL/Python function "python_traceback", line 6, in second third() PL/Python function "python_traceback", line 9, in third plpy.execute("select sql_error()") PL/Python function "python_traceback" SQL statement "select python_traceback()" PL/pgSQL function python_from_sql_error() line 3 at SQL statement 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT python_from_sql_error(); 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error ERROR: spiexceptions.DivisionByZero: division by zero 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "sql_from_python_error", line 2, in plpy.execute("select sql_error()") PL/Python function "sql_from_python_error" 2025-01-05 17:28:38.553 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT sql_from_python_error(); 2025-01-05 17:28:38.563 GMT client backend[5892] pg_regress/plpython_error ERROR: plpy.SPIError: SPI_execute failed: SPI_ERROR_TRANSACTION 2025-01-05 17:28:38.563 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "manual_subxact", line 2, in plpy.execute("savepoint save") PL/Python function "manual_subxact" 2025-01-05 17:28:38.563 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT manual_subxact(); 2025-01-05 17:28:38.564 GMT client backend[5892] pg_regress/plpython_error ERROR: plpy.SPIError: SPI_execute_plan failed: SPI_ERROR_TRANSACTION 2025-01-05 17:28:38.564 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "manual_subxact_prepared", line 4, in plpy.execute(save) PL/Python function "manual_subxact_prepared" 2025-01-05 17:28:38.564 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT manual_subxact_prepared(); 2025-01-05 17:28:38.569 GMT client backend[5892] pg_regress/plpython_error ERROR: error fetching next item from iterator 2025-01-05 17:28:38.569 GMT client backend[5892] pg_regress/plpython_error DETAIL: spiexceptions.InvalidDatetimeFormat: invalid value "xy" for "DD" 2025-01-05 17:28:38.569 GMT client backend[5892] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "python_error_detail" 2025-01-05 17:28:38.569 GMT client backend[5892] pg_regress/plpython_error STATEMENT: SELECT python_error_detail(); 2025-01-05 17:28:39.188 GMT client backend[3112] pg_regress/plpython_ereport LOG: log 2025-01-05 17:28:39.188 GMT client backend[3112] pg_regress/plpython_ereport DETAIL: some detail 2025-01-05 17:28:39.188 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: PL/Python function "elog_test" 2025-01-05 17:28:39.188 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: SELECT elog_test(); 2025-01-05 17:28:39.188 GMT client backend[3112] pg_regress/plpython_ereport WARNING: warning 2025-01-05 17:28:39.188 GMT client backend[3112] pg_regress/plpython_ereport DETAIL: some detail 2025-01-05 17:28:39.188 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: PL/Python function "elog_test" 2025-01-05 17:28:39.189 GMT client backend[3112] pg_regress/plpython_ereport ERROR: plpy.Error: stop on error 2025-01-05 17:28:39.189 GMT client backend[3112] pg_regress/plpython_ereport DETAIL: some detail 2025-01-05 17:28:39.189 GMT client backend[3112] pg_regress/plpython_ereport HINT: some hint 2025-01-05 17:28:39.189 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "elog_test", line 18, in plpy.error('stop on error', detail='some detail', hint='some hint') PL/Python function "elog_test" 2025-01-05 17:28:39.189 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: SELECT elog_test(); 2025-01-05 17:28:39.191 GMT client backend[3112] pg_regress/plpython_ereport ERROR: ValueError: invalid SQLSTATE code 2025-01-05 17:28:39.191 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('wrong sqlstate', sqlstate='54444A') PL/Python anonymous code block 2025-01-05 17:28:39.191 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('wrong sqlstate', sqlstate='54444A') $$ LANGUAGE plpython3u; 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport ERROR: TypeError: 'blabla' is an invalid keyword argument for this function 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('unsupported argument', blabla='fooboo') PL/Python anonymous code block 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('unsupported argument', blabla='fooboo') $$ LANGUAGE plpython3u; 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport ERROR: TypeError: argument 'message' given by name and position 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('first message', message='second message') PL/Python anonymous code block 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('first message', message='second message') $$ LANGUAGE plpython3u; 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport ERROR: TypeError: argument 'message' given by name and position 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('first message', 'second message', message='third message') PL/Python anonymous code block 2025-01-05 17:28:39.192 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('first message', 'second message', message='third message') $$ LANGUAGE plpython3u; 2025-01-05 17:28:39.193 GMT client backend[3112] pg_regress/plpython_ereport ERROR: plpy.Error: hello 2025-01-05 17:28:39.193 GMT client backend[3112] pg_regress/plpython_ereport DETAIL: world 2025-01-05 17:28:39.193 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-01-05 17:28:39.193 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception('hello', 'world'); 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport ERROR: plpy.Error: message text 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport DETAIL: detail text 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception('message text', 'detail text', _sqlstate => 'YY333'); 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport ERROR: plpy.Error: message text 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport DETAIL: detail text 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport HINT: hint text 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception(_message => 'message text', _detail => 'detail text', _hint => 'hint text', _sqlstate => 'XX555', _schema_name => 'schema text', _table_name => 'table text', _column_name => 'column text', _datatype_name => 'datatype text', _constraint_name => 'constraint text'); 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport ERROR: plpy.Error: message text 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport HINT: hint text 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-01-05 17:28:39.194 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception(_message => 'message text', _hint => 'hint text', _schema_name => 'schema text', _column_name => 'column text', _constraint_name => 'constraint text'); 2025-01-05 17:28:39.196 GMT client backend[3112] pg_regress/plpython_ereport ERROR: plpy.SPIError: plpy.Error: my message 2025-01-05 17:28:39.196 GMT client backend[3112] pg_regress/plpython_ereport HINT: some hint 2025-01-05 17:28:39.196 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 6, in raise e PL/Python anonymous code block, line 3, in __plpython_inline_block plpy.execute("select raise_exception(_message => 'my message', _sqlstate => 'XX987', _hint => 'some hint', _table_name => 'users_tab', _datatype_name => 'user_type')") PL/Python anonymous code block 2025-01-05 17:28:39.196 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: DO $$ try: plpy.execute("select raise_exception(_message => 'my message', _sqlstate => 'XX987', _hint => 'some hint', _table_name => 'users_tab', _datatype_name => 'user_type')") except Exception as e: plpy.info(e.spidata) raise e $$ LANGUAGE plpython3u; 2025-01-05 17:28:39.197 GMT client backend[3112] pg_regress/plpython_ereport ERROR: plpy.Error: my message 2025-01-05 17:28:39.197 GMT client backend[3112] pg_regress/plpython_ereport HINT: some hint 2025-01-05 17:28:39.197 GMT client backend[3112] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 6, in raise e PL/Python anonymous code block, line 3, in __plpython_inline_block plpy.error(message = 'my message', sqlstate = 'XX987', hint = 'some hint', table_name = 'users_tab', datatype_name = 'user_type') PL/Python anonymous code block 2025-01-05 17:28:39.197 GMT client backend[3112] pg_regress/plpython_ereport STATEMENT: DO $$ try: plpy.error(message = 'my message', sqlstate = 'XX987', hint = 'some hint', table_name = 'users_tab', datatype_name = 'user_type') except Exception as e: plpy.info('sqlstate: %s, hint: %s, table_name: %s, datatype_name: %s' % (e.sqlstate, e.hint, e.table_name, e.datatype_name)) raise e $$ LANGUAGE plpython3u; 2025-01-05 17:28:39.996 GMT client backend[416] pg_regress/plpython_composite ERROR: length of returned sequence did not match number of columns in row 2025-01-05 17:28:39.996 GMT client backend[416] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "changing_test" 2025-01-05 17:28:39.996 GMT client backend[416] pg_regress/plpython_composite STATEMENT: SELECT * FROM changing_test(); 2025-01-05 17:28:39.996 GMT client backend[416] pg_regress/plpython_composite ERROR: length of returned sequence did not match number of columns in row 2025-01-05 17:28:39.996 GMT client backend[416] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "changing_test" 2025-01-05 17:28:39.996 GMT client backend[416] pg_regress/plpython_composite STATEMENT: SELECT * FROM changing_test(); 2025-01-05 17:28:40.003 GMT client backend[416] pg_regress/plpython_composite ERROR: key "v3" not found in mapping 2025-01-05 17:28:40.003 GMT client backend[416] pg_regress/plpython_composite HINT: To return null in a column, add the value None to the mapping with the key named after the column. 2025-01-05 17:28:40.003 GMT client backend[416] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "return_record_2" 2025-01-05 17:28:40.003 GMT client backend[416] pg_regress/plpython_composite STATEMENT: SELECT * FROM return_record_2('v4') AS (v1 int, v3 int, v2 int); 2025-01-05 17:28:40.006 GMT client backend[416] pg_regress/plpython_composite ERROR: malformed record literal: "first" 2025-01-05 17:28:40.006 GMT client backend[416] pg_regress/plpython_composite DETAIL: Missing left parenthesis. 2025-01-05 17:28:40.006 GMT client backend[416] pg_regress/plpython_composite HINT: To return a composite type in an array, return the composite type as a Python tuple, e.g., "[('foo',)]". 2025-01-05 17:28:40.006 GMT client backend[416] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "composite_type_as_list_broken" 2025-01-05 17:28:40.006 GMT client backend[416] pg_regress/plpython_composite STATEMENT: SELECT * FROM composite_type_as_list_broken(); 2025-01-05 17:28:40.168 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: spiexceptions.InvalidTextRepresentation: invalid input syntax for type integer: "oops" at character 40 2025-01-05 17:28:40.168 GMT client backend[3044] pg_regress/plpython_subtransaction QUERY: INSERT INTO subtransaction_tbl VALUES ('oops') 2025-01-05 17:28:40.168 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_ctx_test", line 6, in plpy.execute("INSERT INTO subtransaction_tbl VALUES ('oops')") PL/Python function "subtransaction_ctx_test" 2025-01-05 17:28:40.168 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_ctx_test('SPI'); 2025-01-05 17:28:40.171 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: Exception: Python exception 2025-01-05 17:28:40.171 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_ctx_test", line 8, in raise Exception("Python exception") PL/Python function "subtransaction_ctx_test" 2025-01-05 17:28:40.171 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_ctx_test('Python'); 2025-01-05 17:28:40.174 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: spiexceptions.SyntaxError: syntax error at or near "error" at character 1 2025-01-05 17:28:40.174 GMT client backend[3044] pg_regress/plpython_subtransaction QUERY: error 2025-01-05 17:28:40.174 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_nested_test", line 8, in plpy.execute("error") PL/Python function "subtransaction_nested_test" 2025-01-05 17:28:40.174 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_nested_test(); 2025-01-05 17:28:40.184 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has not been entered 2025-01-05 17:28:40.184 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_without_enter", line 2, in plpy.subtransaction().__exit__(None, None, None) PL/Python function "subtransaction_exit_without_enter" 2025-01-05 17:28:40.184 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_without_enter(); 2025-01-05 17:28:40.184 GMT client backend[3044] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-01-05 17:28:40.184 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_without_exit" 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_exit_twice" 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has not been entered 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_twice", line 3, in plpy.subtransaction().__exit__(None, None, None) PL/Python function "subtransaction_exit_twice" 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_twice(); 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_twice" 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_twice" 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been exited 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_same_subtransaction_twice", line 5, in s.__exit__(None, None, None) PL/Python function "subtransaction_exit_same_subtransaction_twice" 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_same_subtransaction_twice(); 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-01-05 17:28:40.185 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_same_subtransaction_twice" 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been entered 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_enter_same_subtransaction_twice", line 4, in s.__enter__() PL/Python function "subtransaction_enter_same_subtransaction_twice" 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_enter_same_subtransaction_twice(); 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been entered 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_enter_subtransaction_in_with", line 3, in s.__enter__() PL/Python function "subtransaction_enter_subtransaction_in_with" 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_enter_subtransaction_in_with(); 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been exited 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_subtransaction_in_with", line 6, in raise ValueError(e) PL/Python function "subtransaction_exit_subtransaction_in_with" 2025-01-05 17:28:40.186 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_subtransaction_in_with(); 2025-01-05 17:28:40.189 GMT client backend[3044] pg_regress/plpython_subtransaction WARNING: Caught a SPI error from an explicit subtransaction 2025-01-05 17:28:40.189 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_mix_explicit_and_implicit" 2025-01-05 17:28:40.190 GMT client backend[3044] pg_regress/plpython_subtransaction WARNING: Caught a SPI error 2025-01-05 17:28:40.190 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_mix_explicit_and_implicit" 2025-01-05 17:28:40.207 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: iterating a cursor in an aborted subtransaction 2025-01-05 17:28:40.207 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "cursor_aborted_subxact", line 8, in fetched = cur.fetch(10) PL/Python function "cursor_aborted_subxact" 2025-01-05 17:28:40.207 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT cursor_aborted_subxact(); 2025-01-05 17:28:40.209 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: iterating a cursor in an aborted subtransaction 2025-01-05 17:28:40.209 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "cursor_plan_aborted_subxact", line 10, in fetched = cur.fetch(5) PL/Python function "cursor_plan_aborted_subxact" 2025-01-05 17:28:40.209 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT cursor_plan_aborted_subxact(); 2025-01-05 17:28:40.210 GMT client backend[3044] pg_regress/plpython_subtransaction ERROR: ValueError: closing a cursor in an aborted subtransaction 2025-01-05 17:28:40.210 GMT client backend[3044] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "cursor_close_aborted_subxact", line 7, in cur.close() PL/Python function "cursor_close_aborted_subxact" 2025-01-05 17:28:40.210 GMT client backend[3044] pg_regress/plpython_subtransaction STATEMENT: SELECT cursor_close_aborted_subxact(); 2025-01-05 17:28:40.411 GMT client backend[1592] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: invalid transaction termination 2025-01-05 17:28:40.411 GMT client backend[1592] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python function "transaction_test2", line 5, in plpy.commit() PL/Python function "transaction_test2" 2025-01-05 17:28:40.411 GMT client backend[1592] pg_regress/plpython_transaction STATEMENT: SELECT transaction_test2(); 2025-01-05 17:28:40.412 GMT client backend[1592] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: spiexceptions.InvalidTransactionTermination: invalid transaction termination 2025-01-05 17:28:40.412 GMT client backend[1592] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python function "transaction_test3", line 2, in plpy.execute("CALL transaction_test1()") PL/Python function "transaction_test3" 2025-01-05 17:28:40.412 GMT client backend[1592] pg_regress/plpython_transaction STATEMENT: SELECT transaction_test3(); 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: spiexceptions.InvalidTransactionTermination: invalid transaction termination 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python function "transaction_test4", line 2, in plpy.execute("DO LANGUAGE plpython3u $x$ plpy.commit() $x$") PL/Python function "transaction_test4" 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction STATEMENT: SELECT transaction_test4(); 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction CONTEXT: PL/Python anonymous code block 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: cannot commit while a subtransaction is active 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 4, in plpy.commit() PL/Python anonymous code block 2025-01-05 17:28:40.413 GMT client backend[1592] pg_regress/plpython_transaction STATEMENT: DO LANGUAGE plpython3u $$ s = plpy.subtransaction() s.enter() plpy.commit() $$; 2025-01-05 17:28:40.427 GMT client backend[1592] pg_regress/plpython_transaction ERROR: spiexceptions.DivisionByZero: division by zero 2025-01-05 17:28:40.427 GMT client backend[1592] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 3, in plpy.execute("INSERT INTO test1 (a) VALUES (12/(%s-2))" % row['x']) PL/Python anonymous code block 2025-01-05 17:28:40.427 GMT client backend[1592] pg_regress/plpython_transaction STATEMENT: DO LANGUAGE plpython3u $$ for row in plpy.cursor("SELECT * FROM test2 ORDER BY x"): plpy.execute("INSERT INTO test1 (a) VALUES (12/(%s-2))" % row['x']) plpy.commit() $$; 2025-01-05 17:28:40.443 GMT client backend[1592] pg_regress/plpython_transaction ERROR: spiexceptions.ForeignKeyViolation: insert or update on table "testfk" violates foreign key constraint "testfk_f1_fkey" 2025-01-05 17:28:40.443 GMT client backend[1592] pg_regress/plpython_transaction DETAIL: Key (f1)=(0) is not present in table "testpk". 2025-01-05 17:28:40.443 GMT client backend[1592] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 4, in plpy.commit() PL/Python anonymous code block 2025-01-05 17:28:40.443 GMT client backend[1592] pg_regress/plpython_transaction STATEMENT: DO LANGUAGE plpython3u $$ # this insert will fail during commit: plpy.execute("INSERT INTO testfk VALUES (0)") plpy.commit() plpy.warning('should not get here') $$; 2025-01-05 17:28:41.068 GMT postmaster[1228] LOG: received fast shutdown request 2025-01-05 17:28:41.068 GMT postmaster[1228] 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: 1228 abort() has been called