Source: postgresql-13 Version: 13.0-6 Severity: serious Justification: ftbfs Tags: ftbfs User: debian-p...@lists.debian.org Usertags: perl-5.32-transition Control: block 968912 with -1
Similar to postgresql-12 (#974061) postgresql-13 FTBFS on multiple archs, eg: https://buildd.debian.org/status/fetch.php?pkg=postgresql-13&arch=amd64&ver=13.0-6%2Bb1&stamp=1604915618&raw=0 Unfortunately, postgresql-13 wasn't in sid at the point we did our last full rebuild test. plperl does seem to be implicated in the error output: 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger ERROR: object audit_tbls.schema_two_table_three of type table cannot be dropped 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE SQL statement "DROP TABLE IF EXISTS audit_tbls.schema_two_table_three" PL/pgSQL function test_evtrig_dropped_objects() line 8 at EXECUTE 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger ERROR: object schema_one.table_three of type table cannot be dropped 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2020-11-09 09:53:28.985 UTC client backend[31345] pg_regress/event_trigger ERROR: pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function 2020-11-09 09:53:28.985 UTC client backend[31345] pg_regress/event_trigger STATEMENT: select pg_event_trigger_table_rewrite_oid(); 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger ERROR: rewrites not allowed 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger STATEMENT: alter table rewriteme alter column foo type numeric; 2020-11-09 09:53:29.024 UTC client backend[31345] pg_regress/event_trigger ERROR: cannot alter type "rewritetype" because column "rewritemetoo3.a" uses it 2020-11-09 09:53:29.024 UTC client backend[31345] pg_regress/event_trigger STATEMENT: alter type rewritetype alter attribute a type varchar cascade; 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats LOG: wait_for_stats delayed 0.543818 seconds 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats CONTEXT: PL/pgSQL function wait_for_stats() line 48 at RAISE 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats STATEMENT: SELECT wait_for_stats(); 2020-11-09 09:53:30.836 UTC postmaster[29982] LOG: received fast shutdown request 2020-11-09 09:53:30.836 UTC postmaster[29982] LOG: aborting any active transactions 2020-11-09 09:53:30.839 UTC postmaster[29982] LOG: background worker "logical replication launcher" (PID 29991) exited with exit code 1 2020-11-09 09:53:30.840 UTC checkpointer[29986] LOG: shutting down 2020-11-09 09:53:30.840 UTC checkpointer[29986] LOG: checkpoint starting: shutdown immediate 2020-11-09 09:53:31.100 UTC checkpointer[29986] LOG: checkpoint complete: wrote 10551 buffers (64.4%); 0 WAL file(s) added, 0 removed, 13 recycled; write=0.227 s, sync=0.000 s, total=0.259 s; sync files=0, longest=0.000 s, average=0.000 s; distance=220237 kB, estimate=220237 kB 2020-11-09 09:53:31.131 UTC postmaster[29982] LOG: database system is shut down Please could you take a look? Cheers Dominic
