ELF>0@@AW1AVAUATIH=USH8t$ @t$ AT$pqlfofD$@D$BD$0H$E11DH<$L|$LIuLL,$H|$LLALeH=LHA9\$pHcLHi8IL$hHqIH5HH1H5HI1L1 H{|$ D|$ eL|$0H5LH$H8LH=H1H$HtHEtB1H5|$ t8H51H8[]A\A]A^A_fHT$0H51fDAW1AVAUATUSHHHH|$0H=foSptD$Pe.txfD$TD$@HD$@D$1D$$HD$(fDH|$0HcD$$Hi8HGhHpHD$H5HHD$81HHH5HD$ AH5HAH5HAAEE11iDDHDDHHD$DDHHD$ALD$HL$HHH51D9d$ tvHt)uHD$H5HHP1vfDH|$(H5T$T$HHu8Ht$(H=H1@D$HH|$8Ht$0D$$D$$9FpbHtH|$uHH[]A\A]A^A_H51Ht$@H=1AW1AVAUATUSHHHH|$0H=foD$XHnown.txtHD$PCpD$@HD$@D$1D$$HD$(@H|$0HcD$$Hi8HGhHpHD$H5HHD$81HHH5HD$ AH5HAH5HAAEE11iDDHDDHHD$DDHHD$ALD$HL$HHH51D9d$ tvHt)uHD$H5HHP1vfDH|$(H5T$T$HHu8Ht$(H=H1@D$HH|$8Ht$0D$$D$$9FpbHtH|$uHH[]A\A]A^A_H51Ht$@H=1AW1AAVAUATUSHHXH|$ H=t$,CpGD$(E11DH|$ HcD$(Hi8HGhHpHD$H5HHD$1IHH5LH5LD$ AƅE11afDDDLHT$ DLH$HH $H5HH1AD9EuHtKuLL$0LL $HD$L $HpLH|$0HL $LSH5H=$$HHu8H5H=H1fL$$D AutAH|$H\$ D$(D$(9CpEHtHEth1H5|$,taHXH51[]A\A]A^A_H|$H51HrLeHX[]A\A]A^A_HXHH51[]A\A]A^A_Checking for large objectscountwcould not open file "%s": %s warningnspnamerelnameattnameDatabase: %s %s.%s.%s fatal Checking for hash indexesreindex_hash.sqlREINDEX INDEX %s.%s; SELECT count(*) FROM pg_catalog.pg_largeobject SELECT pg_catalog.lo_create(t.loid) FROM (SELECT DISTINCT loid FROM pg_catalog.pg_largeobject) AS t; Your installation contains large objects. The new database has an additional large object permission table. After upgrading, you will be given a command to populate the pg_largeobject_metadata table with default permissions. Your installation contains large objects. The new database has an additional large object permission table, so default permissions must be defined for all large objects. The file %s when executed by psql by the database superuser will set the default permissions. Checking for incompatible "line" data typeSELECT n.nspname, c.relname, a.attname FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalog.pg_attribute a WHERE c.oid = a.attrelid AND NOT a.attisdropped AND a.atttypid = 'pg_catalog.line'::pg_catalog.regtype AND c.relnamespace = n.oid AND n.nspname !~ '^pg_temp_' AND n.nspname !~ '^pg_toast_temp_' AND n.nspname NOT IN ('pg_catalog', 'information_schema')Your installation contains the "line" data type in user tables. This data type changed its internal and input/output format between your old and new clusters so this cluster cannot currently be upgraded. You can remove the problem tables and restart the upgrade. A list of the problem columns is in the file: %s Checking for invalid "unknown" user columnsSELECT n.nspname, c.relname, a.attname FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalog.pg_attribute a WHERE c.oid = a.attrelid AND NOT a.attisdropped AND a.atttypid = 'pg_catalog.unknown'::pg_catalog.regtype AND c.relkind IN ('r', 'c', 'm') AND c.relnamespace = n.oid AND n.nspname !~ '^pg_temp_' AND n.nspname !~ '^pg_toast_temp_' AND n.nspname NOT IN ('pg_catalog', 'information_schema')Your installation contains the "unknown" data type in user tables. This data type is no longer allowed in tables, so this cluster cannot currently be upgraded. You can remove the problem tables and restart the upgrade. A list of the problem columns is in the file: %s SELECT n.nspname, c.relname FROM pg_catalog.pg_class c, pg_catalog.pg_index i, pg_catalog.pg_am a, pg_catalog.pg_namespace n WHERE i.indexrelid = c.oid AND c.relam = a.oid AND c.relnamespace = n.oid AND a.amname = 'hash'UPDATE pg_catalog.pg_index i SET indisvalid = false FROM pg_catalog.pg_class c, pg_catalog.pg_am a, pg_catalog.pg_namespace n WHERE i.indexrelid = c.oid AND c.relam = a.oid AND c.relnamespace = n.oid AND a.amname = 'hash' Your installation contains hash indexes. These indexes have different internal formats between your old and new clusters, so they must be reindexed with the REINDEX command. After upgrading, you will be given REINDEX instructions. Your installation contains hash indexes. These indexes have different internal formats between your old and new clusters, so they must be reindexed with the REINDEX command. The file %s when executed by psql by the database superuser will recreate all invalid indexes; until then, none of these indexes will be used. pg_largeobject.stables_using_lintables_using_unkGCC: (Debian 10.2.1-6) 10.2.1 20210110zRx L*BDB B(K0A8G 8A0A(B BBBD Ll_BDB B(A0A8J  8A0A(B BBBA L_BDB B(A0A8J  8A0A(B BBBA | BGB B(A0A8G 8O0A(B BBBE q 8A0A(B BBBE D8Q0F(B BBB  0$!)#.A38=CIOIUQ[Yaogam{sPy xh  X *,2BIQZj|0_ _Iiversion.c.LC0.LC9.LC5.LC1.LC2.LC3.LC4.LC6.LC7.LC8.LC10.LC19.LC11.LC12.LC13.LC14.LC16.LC15.LC17.LC18.LC20.LC23.LC21.LC22.LC24.LC25.LC27.LC26.LC29.LC28.LC30new_9_0_populate_pg_largeobject_metadata_GLOBAL_OFFSET_TABLE_prep_statusinitPQExpBufferappendPsqlMetaConnectfputstermPQExpBufferfwritePQclearPQfinishconnectToServerexecuteQueryOrDiePQfnumberPQgetvaluestrtolfopen__errno_locationstrerrorpg_fatalfclosereport_statuspg_logcheck_okold_9_3_check_for_line_data_type_usagePQntuplesfprintfold_9_6_check_for_unknown_data_type_usageold_9_6_invalidate_hash_indexesquote_identifier ',9 |-./0 1234 5"6.7=8hp9:;<=>?@$?NS,[45B666B7U7l7CC9:;<2#3G=S@lx?<,4& 55@BGV6]h6oz6777C C099K:R;^h<y23=@?!<",W4^#m5xB667F7F$C.-C.P/\0kr%z9:;%<23=  >& &H 'O 5W 2d 2 % (< ?| @ ? p0.symtab.strtab.shstrtab.rela.text.data.bss.rodata.str1.1.rodata.str1.8.rodata.cst16.comment.note.GNU-stack.rela.eh_frame @ @X"h & , 12 @2 OP0]0(f{v@/` 0 * z 0