Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 88

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 215

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 216

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 217

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 218

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 219

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 220
Ț•<[\ÈÉÌ èÏóhĂ],ߊ'j-’eÀ#&SJ^ž ęÀëßEË ć"!""+"?"S"U"Ÿ]":ę"A8#;z#J¶#E$AG$G‰$AŃ$K%;_%S›%Mï%J=&Eˆ&GÎ&@'ąW'ú' ( (.(E(^( {(!œ(Ÿ(Ę(%ű())H)'f)Ž)­)É)Ț)$û) *;*Y*%v*$œ*Á*Ú*"ß*#+&+?+B+F+W+*r+-+eË+%1,BW,Oš,ê,%-**-5U-‹-Ș-+Ä-*đ-+.G./b."’.+”.+á.& /:4/Jo/Rș/ 0*0àG0"(1K1&k1%’1 ž1Æ17á126+26b2$™2Ÿ2KÛ2''3PO3P 3Kń39=4tw4 ì4<ö4b35\–5?ó536.J6+y6„6EŸ6757&S7 z74›75Đ7"8*)8T82p86Ł84Ú8<9.L9~{92ú96-:4d:<™:.Ö:~;i„;iî;#X<E|<8Â<Mû<&I=p=Œ=M”=[â=>>>t}>…ò>4x@&­AÔB@îC/ECFLIG–G:±G<ìG*)H+TH#€H€H!¶HŰH2îHD!IDfI“«I$?J#dJ ˆJ&©J(ĐJ(ùJ*"K/MK,}KȘK)ÊKôK!L"4L*WL-‚L!°L+ÒL>țLC=M8MEșMCNCDNCˆNDÌNFOBXO›O*ȘO!ŐO"śOP!P:PFSPDšP?ßPQ5QRQnQ6‡QŸQĆQBÈQG RISR{RCS@]SPžSQïSRATO”TVäT;UWU=pU9źU/èUV?'V?gVH§V+đVW)4W(^WV‡W3ȚWX(Xą0XÓYÖYòYŃZvÔZqK[ćœ[(Ł\2Ì\}ÿ\%}_UŁ_bù_\`ŸbaÜ!b7țb 6dśCe);fefwfˆfŠf©’fAš‚`ç‚/Hƒ#xƒ œƒOȘƒcúƒE^„f€„š …=Ž†Tò‡*G‰XrŠ"ˋîŒFđ"7ŽEZŽH Ž2éŽ+$Hm(„­:ƏHGJ‘’#$‘!H‘ j‘%‹‘(±‘*ڑ+’11’4c’(˜’-Á’ï’# “"1“+T“6€“%·“9ʓ@”=X”;–”GҔH•Gc•O«•Hû•GD–EŒ– Җ6ܖ*—5>—t—|—–—Kł—Iÿ—CI˜˜"„˜Șâ˜3ù˜-™3™F6™P}™RΙ”!šL¶šB›YF›T ›Ző›WPœ`šœ %?>?~4ŸóOžNSžLąž-%8Ÿ-^Ÿ_ŒŸ<ìŸ) E VÍ-Y0@b=Iӄäpÿ_aW,ĐyÁûduƒț9eŻv\cúđ!.·wĂźĘÎB óËE5Pî$±4~Š»<LFˆŃ­U] |Ÿ%Ěš>i1‘R[◜({ńsH‹qèXC  ùNȚŐO‡™TÔ€l&Æté6ąÈzŠüĆÖí 'ÊK}#ò›€…ÚÒ:ᔩJhśżZx2mDŸŰȘŒćșGfÜ;ëÙæ†űŚ°ÌoQ§*73«ČßSjŁ"’M•gž8Ą/‚ωô”ŹkŒ„ę +`ÉnŽ–ă^?˜¶œrčÂÀŽ“àžAìőÛÇö)çêłï *Clusters are compatible* *failure* Before running pg_upgrade you must: create a new database cluster (using the new version of initdb) shutdown the postmaster servicing the old cluster shutdown the postmaster servicing the new cluster For example: pg_upgrade -d oldCluster/data -D newCluster/data -b oldCluster/bin -B newCluster/bin or If pg_upgrade fails after this point, you must re-initdb the new cluster before continuing. If you want to start the old cluster, you will need to remove the ".old" suffix from %s/global/pg_control.old. Because "link" mode was used, the old cluster cannot be safely started once the new cluster has been started. Performing Upgrade ------------------ Report bugs to . The old cluster has a "plpython_call_handler" function defined in the "public" schema which is a duplicate of the one defined in the "pg_catalog" schema. You can confirm this by executing in psql: \df *.plpython_call_handler The "public" schema version of this function was created by a pre-8.1 install of plpython, and must be removed for pg_upgrade to complete because it references a now-obsolete "plpython" shared object file. You can remove the "public" schema version of this function by running the following command: DROP FUNCTION public.plpython_call_handler() in each affected database: Upgrade Complete ---------------- WARNING: new data directory should not be inside the old data directory, e.g. %s WARNING: user-defined tablespace locations should not be inside the data directory, e.g. %s When you run pg_upgrade, you must provide the following information: the data directory for the old cluster (-d DATADIR) the data directory for the new cluster (-D DATADIR) the "bin" directory for the old version (-b BINDIR) the "bin" directory for the new version (-B BINDIR) Your installation contains extensions that should be updated with the ALTER EXTENSION command. The file %s when executed by psql by the database superuser will update these extensions. 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. 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. 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. connection to database failed: %s source databases: target databases: %s $ export PGDATAOLD=oldCluster/data $ export PGDATANEW=newCluster/data $ export PGBINOLD=oldCluster/bin $ export PGBINNEW=newCluster/bin $ pg_upgrade -?, --help show this help, then exit -B, --new-bindir=BINDIR new cluster executable directory -D, --new-datadir=DATADIR new cluster data directory -O, --new-options=OPTIONS new cluster options to pass to the server -P, --new-port=PORT new cluster port number (default %d) -U, --username=NAME cluster superuser (default "%s") -V, --version display version information, then exit -b, --old-bindir=BINDIR old cluster executable directory -c, --check check clusters only, don't change any data -d, --old-datadir=DATADIR old cluster data directory -j, --jobs=NUM number of simultaneous processes or threads to use -k, --link link instead of copying files to new cluster -o, --old-options=OPTIONS old cluster options to pass to the server -p, --old-port=PORT old cluster port number (default %d) -r, --retain retain SQL and log files after success -v, --verbose enable verbose internal logging C:\> set PGDATAOLD=oldCluster/data C:\> set PGDATANEW=newCluster/data C:\> set PGBINOLD=oldCluster/bin C:\> set PGBINNEW=newCluster/bin C:\> pg_upgrade WAL block size WAL segment size block size checkpoint next XID data checksum version dates/times are integers? first WAL segment after reset float8 argument passing method large relation segment size large-object chunk size latest checkpoint next MultiXactId latest checkpoint next MultiXactOffset latest checkpoint next OID latest checkpoint oldest MultiXactId latest checkpoint oldestXID maximum TOAST chunk size maximum alignment maximum identifier length maximum number of indexed columns pg_upgrade [OPTION]... which is an index on "%s.%s" which is an index on OID %u which is the TOAST table for "%s.%s" which is the TOAST table for OID %u"%s" is not a directory %-*s%d: controldata retrieval problem %d: database cluster state problem %d: pg_resetwal problem %s%s %s.%s: %u to %u %s: cannot be run as root %s: could not find own program executable Adding ".old" suffix to old global/pg_controlAll non-template0 databases must allow connections, i.e. their pg_database.datallowconn must be true Analyzing all rows in the new clusterCannot continue without required control information, terminating Cannot upgrade to/from the same system catalog version when using tablespaces. Checking cluster versionsChecking database connection settingsChecking database user is the install userChecking for contrib/isn with bigint-passing mismatchChecking for extension updatesChecking for hash indexesChecking for incompatible "jsonb" data typeChecking for incompatible "line" data typeChecking for invalid "unknown" user columnsChecking for large objectsChecking for new cluster tablespace directoriesChecking for prepared transactionsChecking for presence of required librariesChecking for reg* data types in user tablesChecking for roles starting with "pg_"Checking for system-defined composite types in user tablesConsult the last few lines of "%s" for the probable cause of the failure. Consult the last few lines of "%s" or "%s" for the probable cause of the failure. Copying old %s to new serverCopying user relation files Could not create a script to delete the old cluster's data files because user-defined tablespaces or the new cluster's data directory exist in the old cluster directory. The old cluster's contents must be deleted manually. Creating dump of database schemas Creating dump of global objectsCreating script to analyze new clusterCreating script to delete old clusterDatabase: %s Deleting files from new %sFailed to match up old and new tables in database "%s" Failure, exiting Finding the real data directory for the source clusterFinding the real data directory for the target clusterFreezing all rows in the new clusterLinking user relation files New cluster data and binary directories are from different major versions. New cluster database "%s" is not empty No match found in new cluster for old relation with OID %u in database "%s": %s No match found in old cluster for new relation with OID %u in database "%s": %s Old cluster data and binary directories are from different major versions. Only the install user can be defined in the new cluster. Optimizer statistics are not transferred by pg_upgrade so, once you start the new server, consider running: %s Options: Performing Consistency Checks ----------------------------- Performing Consistency Checks on Old Live Server ------------------------------------------------ Relation names for OID %u in database "%s" do not match: old name "%s.%s", new name "%s.%s" Remove the problem functions from the old cluster to continue. Resetting WAL archivesRestoring database schemas in the new cluster Restoring global objects in the new clusterRunning in verbose mode Running this script will delete the old cluster's data files: %s SQL command failed %s %sSetting frozenxid and minmxid counters in new clusterSetting minmxid counter in new clusterSetting next OID for new clusterSetting next multixact ID and offset for new clusterSetting next transaction ID and epoch for new clusterSetting oldest XID for new clusterSetting oldest multixact ID in new clusterSync data directory to diskThe source cluster contains prepared transactions The source cluster contains roles starting with "pg_" The source cluster lacks cluster state information: The source cluster lacks some required control information: The source cluster was not shut down cleanly. The source cluster was shut down while in recovery mode. To upgrade, use "rsync" as documented or shut it down as a primary. The target cluster contains prepared transactions The target cluster contains roles starting with "pg_" The target cluster lacks cluster state information: The target cluster lacks some required control information: The target cluster was not shut down cleanly. The target cluster was shut down while in recovery mode. To upgrade, use "rsync" as documented or shut it down as a primary. There seems to be a postmaster servicing the new cluster. Please shutdown that postmaster and try again. There seems to be a postmaster servicing the old cluster. Please shutdown that postmaster and try again. There were problems executing "%s" This utility can only upgrade from PostgreSQL version 8.4 and later. This utility can only upgrade to PostgreSQL version %s. This utility cannot be used to downgrade to older major PostgreSQL versions. Try "%s --help" for more information. Unable to rename %s to %s. Usage: When checking a live server, the old and new port numbers must be different. When checking a pre-PG 9.1 live old server, you must specify the old server's port number. You must have read and write access in the current directory. You must identify the directory where the %s. Please use the %s command-line option or the %s environment variable. Your installation contains "contrib/isn" functions which rely on the bigint data type. Your old and new clusters pass bigint values differently so this cluster cannot currently be upgraded. You can manually upgrade databases that use "contrib/isn" facilities and remove "contrib/isn" from the old cluster and restart the upgrade. A list of the problem functions is in the file: %s Your installation contains one of the reg* data types in user tables. These data types reference system OIDs that are not preserved by pg_upgrade, 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 Your installation contains system-defined composite type(s) in user tables. These type OIDs are not stable across PostgreSQL versions, so this cluster cannot currently be upgraded. You can drop the problem columns and restart the upgrade. A list of the problem columns is in the file: %s Your installation contains the "jsonb" data type in user tables. The internal format of "jsonb" changed during 9.4 beta 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 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 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 Your installation references loadable libraries that are missing from the new installation. You can add these libraries to the new installation, or remove the functions using them from the old installation. A list of problem libraries is in the file: %s cannot run pg_upgrade from inside the new cluster data directory on Windows check for "%s" failed: %s check for "%s" failed: cannot execute (permission denied) check for "%s" failed: cannot read file (permission denied) check for "%s" failed: not a regular file child process exited abnormally: status %d child worker exited abnormally: %s command too long connection to database failed: %scopying "%s" to "%s" could not add execute permission to file "%s": %s could not connect to source postmaster started with the command: %s could not connect to target postmaster started with the command: %s could not create hard link between old and new data directories: %s In link mode the old and new data directories must be on the same file system. could not create worker process: %s could not create worker thread: %s could not delete directory "%s" could not determine current directory could not determine the number of users could not get control data using %s: %s could not get data directory using %s: %s could not get pg_ctl version data using %s: %s could not get pg_ctl version output from %s could not load library "%s": %scould not open file "%s" for reading: %s could not open file "%s": %s could not open version file "%s" could not parse version file "%s" could not read line %d from file "%s": %s could not stat tablespace directory "%s": %s could not write to log file "%s" database user "%s" is not the install user encodings for database "%s" do not match: old "%s", new "%s" error while checking for file existence "%s.%s" ("%s" to "%s"): %s error while copying relation "%s.%s" ("%s" to "%s"): %s error while copying relation "%s.%s": could not create file "%s": %s error while copying relation "%s.%s": could not open file "%s": %s error while copying relation "%s.%s": could not read file "%s": %s error while copying relation "%s.%s": could not stat file "%s": %s error while copying relation "%s.%s": could not write file "%s": %s error while copying relation "%s.%s": partial page found in file "%s" error while creating link for relation "%s.%s" ("%s" to "%s"): %s executing: %s failed to get system locale name for "%s" failed to get the current locale failed to restore old locale "%s" fatal invalid new port number invalid old port number lc_collate values for database "%s" do not match: old "%s", new "%s" lc_ctype values for database "%s" do not match: old "%s", new "%s" libpq environment variable %s has a non-local server value: %s linking "%s" to "%s" mappings for database "%s": new cluster binaries residenew cluster data residesnew cluster tablespace directory already exists: "%s" noticeokold and new cluster pg_controldata checksum versions do not match old and new pg_controldata WAL block sizes are invalid or do not match old and new pg_controldata WAL segment sizes are invalid or do not match old and new pg_controldata alignments are invalid or do not match Likely one cluster is a 32-bit install, the other 64-bit old and new pg_controldata block sizes are invalid or do not match old and new pg_controldata date/time storage types do not match old and new pg_controldata large-object chunk sizes are invalid or do not match old and new pg_controldata maximum TOAST chunk sizes are invalid or do not match old and new pg_controldata maximum identifier lengths are invalid or do not match old and new pg_controldata maximum indexed columns are invalid or do not match old and new pg_controldata maximum relation segment sizes are invalid or do not match old cluster binaries resideold cluster data residesold cluster does not use data checksums but the new one does old cluster uses data checksums but the new one does not old database "%s" not found in the new cluster out of memory pg_ctl failed to start the source server, or connection failed pg_ctl failed to start the target server, or connection failed pg_upgrade upgrades a PostgreSQL cluster to a different major version. relname: %s.%s: reloid: %u reltblspace: %s rewriting "%s" to "%s" tablespace directory "%s" does not exist tablespace path "%s" is not a directory template0 must not allow connections, i.e. its pg_database.datallowconn must be false user-supplied old port number %hu corrected to %hu waitpid() failed: %s warningProject-Id-Version: PostgreSQL 10 Report-Msgid-Bugs-To: pgsql-bugs@postgresql.org POT-Creation-Date: 2022-02-15 18:06+0000 PO-Revision-Date: 2021-11-09 06:33+0100 Last-Translator: Dennis Björklund Language-Team: Swedish Language: sv MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=n != 1; *Klustren Ă€r kompatibla* *misslyckande* Innan du kör pg_upgrade mĂ„ste du: skapa ett nytt databaskluster (med nya versionens initdb) stĂ€nga ner den postmaster som hanterar gamla klustret stĂ€nga ner den postmaster som hanterar nya klustret Till exempel: pg_upgrade -d gammaltKluster/data -D nyttKluster/data -b gammaltKluster/bin -B nyttKluster/bin eller Om pg_upgrade misslyckas efter denna punkt sĂ„ mĂ„ste du köra om initdb pĂ„ nya klustret innan du fortsĂ€tter. Om du vill starta gamla klustret sĂ„ mĂ„ste du ta bort ".old"-suffixet frĂ„n %s/global/pg_control.old. Detta dĂ„ "link"-lĂ€ge anvĂ€ndes och gamla klustret kan inte startas pĂ„ ett sĂ€kert sĂ€tt efter att nya klustret startats. Utför uppgradering ------------------ Rapportera fel till . Det gamla klustret har en "plpython_call_handler"-funktion definierad i "public"-schemat vilket Ă€r en kopia pĂ„ den som definierats i "pg_catalog"-schemat. Du kan verifiera detta genom att i psql köra: \df *.plpython_call_handler "public"-schema-versionen av denna funktion har skapats av en pre-8.1-installation av plpython och mĂ„ste raderas för att pg_upgrade skall kunna gĂ„ klart dĂ„ den referar till en nu förĂ„ldrad "plpython" delad objektfil. Du kan ta bort "public"-schemaversionen av denna funktion genom att köra följande kommando: DROP FUNCTION public.plpython_call_handler() i varje inblandad databas: Uppgradering klar ----------------- VARNING: nya datakatalogen skall inte ligga inuti den gamla datakatalogen, dvs. %s VARNING: anvĂ€ndardefinierade tabellutrymmens position skall inte vara i datakatalogen, dvs. %s NĂ€r du kör pg_upgrade mĂ„ste du ange följande information: datakatalogen för gamla klustret (-d DATAKAT) datakatalogen för nya klustret (-D DATAKAT) "bin"-katalogen för gamla versionen (-b BINKAT) "bin"-katalogen för nya versionen (-B BINKAT) Din installation innehĂ„ller utökningar som skall updateras med kommandot ALTER EXTENSION. Filen %s kan köras med psql av databasens superuser och kommer uppdatera dessa utökningar. Din installation innehĂ„ller hash-index. Dessa index har olika internt format i ditt gamla och nya kluster sĂ„ de mĂ„ste omindexeras med kommandot REINDEX. Efter uppgraderingen sĂ„ kommer du fĂ„ REINDEX-instruktioner. Din installation innehĂ„ller hash-index. Dessa index har olika internt format i ditt gamla och nya kluster sĂ„ de mĂ„ste omindexeras med kommandot REINDEX. Filen %s kan köras med psql av databasens superuser och kommer Ă„terskapa alla ogiltiga index; innan dess sĂ„ kommer inget av dess index anvĂ€ndas. Din installation innehĂ„ller stora objekt. Den nya databasen har en extra rĂ€ttighetstabell för stora onbjekt sĂ„ standardrĂ€ttigheter mĂ„ste ges för alla stora objekt. Filen %s kan köras med psql av databasens superuser för att sĂ€tta standardrĂ€ttigheter. Din installation innehĂ„ller stora objekt. Den nya databasen har en extra rĂ€ttighetstabell för stora objekt. Efter uppgradering kommer du ges ett kommando för att populera rĂ€ttighetstabellen pg_largeobject_metadata med standardrĂ€ttigheter. anslutning till databas misslyckades: %s kĂ€lldatabaser: mĂ„ldatabaser: %s $ export PGDATAOLD=gammaltKluster/data $ export PGDATANEW=nyttKluster/data $ export PGBINOLD=gammaltKluster/bin $ export PGBINNEW=nyttKluster/bin $ pg_upgrade -?, --help visa denns hjĂ€lp, avsluta sedan -B, --new-bindir=BINKAT nya klustrets katalog för körbara filer -D, --new-datadir=DATAKAT nya klustrets datakatalog -O, --new-options=FLAGGOR serverflaggor för nya klustret -P, --new-port=PORT nya klustrets portnummer (standard %d) -U, --username=NAMN klustrets superuser (standard "%s") -V, --version visa versionsinformation, avsluta sedan -b, --old-bindir=BINKAT gamla klustrets katalog för körbara filer -c, --check testa klustren bara, Ă€ndra ingen data -d, --old-datadir=DATAKAT gamla klustrets datakatalog -j, --jobs=NUM antal samtidiga processer eller trĂ„dar att anvĂ€nda -k, --link lĂ€nka istĂ€llet för att kopiera filer till nya klustret -o, --old-options=FLAGGOR serverflaggor för gamla klustret -p, --old-port=PORT gamla klustrets portnummer (standard %d) -r, --retain behĂ„ll SQL och loggfiler efter lyckad uppgradering -v, --verbose slĂ„ pĂ„ utförligt intern loggning C:\> set PGDATAOLD=gammaltKluster/data C:\> set PGDATANEW=nyttKluster/data C:\> set PGBINOLD=gammaltKluster/bin C:\> set PGBINNEW=nyttKluster/bin C:\> pg_upgrade WAL-blockstorlek WAL-segmentstorlek blockstorlek checkpoint nĂ€sta-XID datachecksumversion datum/tid Ă€r heltal? första WAL-segmentet efter reset float8 argumentöverföringsmetod stora relationers segmentstorlek stora-objekt chunkstorlek senaster checkpoint nĂ€sta-MultiXactId senaste checkpoint nĂ€sta-MultiXactOffset senaste checkpoint nĂ€sta-OID senaste checkpoint Ă€ldsta-MultiXactId senaste checkpoint Ă€ldsta-XID maximal TOAST-chunkstorlek maximal alignment maximal identifierarlĂ€ngd maximalt antal indexerade kolumner pg_upgrade [FLAGGA]... vilket Ă€r ett index för "%s.%s" vilket Ă€r ett index för OID %u vilket Ă€r TOAST-tabellen för "%s.%s" vilket Ă€r TOAST-tabellen för OID %u"%s" Ă€r inte en katalog %-*s%d: problem vid hĂ€mtning av kontrolldata %d: state-problem för databaskluster %d: pg_resetwal-problem %s%s %s.%s: %u till %u %s: kan inte köras som root %s: kunde inte hitta det egna programmets körbara fil LĂ€gger till ".old"-suffix till gamla global/pg_controlAlla icke-template0-databaser mĂ„ste tillĂ„ta anslutningar, dvs. deras pg_database.datallowconn mĂ„ste vara true Analyserar alla rader i nya klustretKan inte fortsĂ€tta utan kontrollinformation som krĂ€vs, avslutar Kan inte uppgradera till/frĂ„n samma systemkatalogversion nĂ€r man anvĂ€nder tablespace. Kontrollerar klustrets versionerKontrollerar databasens anslutningsinstĂ€llningarKontrollerar att databasanvĂ€ndaren Ă€r installationsanvĂ€ndarenLetar efter contrib/isn med bigint-anropsfelLetar efter uppdatering av utökningarLetar efter hash-indexLetar efter inkompatibel "jsonb"-datatypLetar efter inkompatibel "line"-datatypLetar efter ogiltiga anvĂ€ndarkolumner av typen "unknown"Letar efter stora objektLetar efter nya tablespace-kataloger i klustretLetar efter förberedda transaktionerKontrollerar att krĂ€vda lĂ€nkbibliotek finnsLetar efter reg*-datatyper i anvĂ€ndartabellerLetar efter roller som startar med "pg_"Letar i anvĂ€ndartabeller efter systemdefinierade typer av sorten "composite"Se de sista raderna i "%s" för en trolig orsak till misslyckandet. Se de sista raderna i "%s" eller "%s" för en trolig orsak till misslyckandet. Kopierar gammal %s till ny serverKopierar anvĂ€ndares relationsfiler Kunde inte skapa ett script som raderar gamla klustrets datafiler dĂ„ anvĂ€ndardefinierade tabellutrymmen eller nya klustrets datakatalog ligger i gamla klusterkatalogen. Det gamla klustrets innehĂ„ll mĂ„ste raderas för hand. Skapar dump med databasscheman Skapar dump med globala objektSkapar skript för att analysera nya klustretSkapar skript för att radera gamla klustretDatabas: %s Raderar filer frĂ„n ny %sMisslyckades med att matcha ihop gamla och nya tabeller i databas "%s" Misslyckades, avslutar Letar efter den riktiga datakatalogen i kĂ€llklustretLetar efter den riktiga datakatalogen för mĂ„lklustretFryser alla rader i nya klustretLĂ€nkar anvĂ€ndares relationsfiler Nya klusterdata och binĂ€ra kataloger Ă€r frĂ„n olika major-versioner. Nya databasklustret "%s" Ă€r inte tomt Ingen trĂ€ff hittad i nya klustret för gammal relation med OID %u i databas "%s": %s Ingen trĂ€ff hittad i gamla klustret för ny relation med OID %u i databas "%s": %s Gammal klusterdata och binĂ€ra kataloger Ă€r frĂ„n olika major-versioner. Bara installationsanvĂ€ndaren fĂ„r finnas i nya klustret. Optimeringsstatistik överförs inte av pg_upgrade sĂ„ nĂ€r du startar nya servern sĂ„ vill du nog köra: %s Flaggor: Utför konsistenskontroller -------------------------- Utför konsistenskontroller pĂ„ gamla live-servern ------------------------------------------------ Relationsname för OID %u i databas "%s" matchar inte: gammalt namn "%s.%s", nytt namn "%s.%s" Ta bort problemfunktionerna frĂ„n gamla klustret för att fortsĂ€tta. Resettar WAL-arkivÅterstĂ€ller databasscheman i nya klustret ÅterstĂ€ller globala objekt i nya klustretKör i utförligt lĂ€ge NĂ€r detta skript körs sĂ„ raderas gamla klustrets datafiler: %s SQL-kommando misslyckades %s %sSĂ€tter rĂ€knarna frozenxid och minmxid för nytt klusterSĂ€tter rĂ€knarenm minmxid för nytt klusterSĂ€tter nĂ€sta OID för nya klustretSĂ€tter nĂ€sta multixact-ID och offset för nytt klusterSĂ€tter nĂ€sta transaktions-ID och epoch för nytt klusterSĂ€tter Ă€ldsta XID för nya klustretSĂ€tter Ă€ldsta multixact-ID i nytt klusterSynkar datakatalog till diskKĂ€llklustret innehĂ„ller förberedda transaktioner KĂ€llklustret innehĂ„ller roller som startar med "pg_" KĂ€llklustret saknar information om kluster-state: KĂ€llklustret saknar lite kontrolldata som krĂ€vs: KĂ€llklustret har inte stĂ€ngts ner pĂ„ ett korrekt sĂ€tt. KĂ€llklustret stĂ€ngdes ner nĂ€r det var i Ă„terstĂ€llningslĂ€ge. För att uppgradera sĂ„ anvĂ€nd "rsync" enligt dokumentation eller stĂ€ng ner den som en primĂ€r. MĂ„lklustret innehĂ„ller förberedda transaktioner MĂ„lklustret innehĂ„ller roller som startar med "pg_" MĂ„lklustret saknar information om kluster-state: MĂ„lklustret saknar lite kontrolldata som krĂ€vs: MĂ„lklustret har inte stĂ€ngts ner pĂ„ ett korrekt sĂ€tt. MĂ„lklustret stĂ€ngdes ner nĂ€r det var i Ă„terstĂ€llningslĂ€ge. För att uppgradera sĂ„ anvĂ€nd "rsync" enligt dokumentation eller stĂ€ng ner den som en primĂ€r. Det verkar vara en postmaster igĂ„ng som hanterar nya klustret. StĂ€nga ner den postmastern och försök igen. Det verkar vara en postmaster igĂ„ng som hanterar gamla klustret. StĂ€nga ner den postmastern och försök igen. Det var problem med att köra "%s" Detta verktyg kan bara uppgradera frĂ„n PostgreSQL version 8.4 eller nyare. Detta verktyg kan bara uppgradera till PostgreSQL version %s. Detta verktyg kan inte anvĂ€ndas för att nergradera till Ă€ldre major-versioner av PostgreSQL. Försök med "%s --help" för mer information. Kan inte byta namn pĂ„ %s till %s. AnvĂ€ndning: Vid kontroll av en live-server sĂ„ mĂ„ste gamla och nya portnumren vara olika. Vid kontroll av en gammal live-server före PG 9.1 sĂ„ mĂ„ste den gamla serverns portnummer anges. Du mĂ„ste ha lĂ€s och skrivrĂ€ttigheter till den aktuella katalogen. Du mĂ„ste identifiera katalogen dĂ€r %s. AnvĂ€nd kommandoradsflaggan %s eller omgivningsvariabeln %s. Din installation innehĂ„ller "contrib/isn"-funktioner sin beror pĂ„ datatypen bigint. Ditt gamla och nya kluster skickar bigint-vĂ€rden pĂ„ olika sĂ€tt sĂ„ detta kluster kan för nĂ€rvarande inte uppgraderas. Du kan manuellt uppgradera databaser som anvĂ€nder "contrib/isn"-finesser genom att radera "contrib/isn" frĂ„n gamla klustret och Ă„terstarta uppgraderingen. En lista med problemfunktionerna finns i filen: %s Din installation anvĂ€nder en av reg*-datatyperna i en anvĂ€ndartabell. Dessa datatyper refererar system-OID:er som inte bevaras av pg_upgrade sĂ„ detta kluster kan för nĂ€rvarande inte uppgraderas. Du kan ta bort problemtabellerna och starta om uppgraderingen. En lista med problemkolumnerna finns i filen: %s Din installation innehĂ„ller anvĂ€ndartabeller med systemdefinierade typer av sorten "composite". OID:er för dessa typer Ă€r inte stabila över PostgreSQL-versioner sĂ„ detta kluster kan inte uppgraderas för tillfĂ€llet. Du kan slĂ€nga problemkolumnerna och Ă„terstarta uppgraderingen. En lista med problemkolumner finns i filen: %s Din installation innehĂ„ller "jsonb"-datatypen i anvĂ€ndartabeller. Interna formatet för "jsonb" Ă€ndrades under 9.4-betan sĂ„ detta kluster kan för nĂ€rvarande inte uppgraderas. Du kan ta bort problemtabellerna och starta om uppgraderingen. En lista med problemkolumnerna finns i filen: %s Din installation innehĂ„ller datatypen "line" i anvĂ€ndartabeller. Denna datatype har Ă€ndrat sitt interna format samt sitt in/ut-format mellan ditt gamla och nya kluster sĂ„ detta kluster kan för nĂ€rvarande inte uppgraderas. Du kan radera problemtabellerna och Ă„terstarta uppgraderingen. En lista med problemkolumner finns i filen: %s Din installation innehĂ„ller anvĂ€ndartabeller med datatypen "unknown". Denna typ tillĂ„ts inte lĂ€ngre i tabeller sĂ„ detta kluster kan för nĂ€rvarande inte uppgraderas. Du kan radera problemtabellerna och Ă„terstarta uppgraderingen. En lista med problemkolumnerna finns i filen: %s Din installation refererar till laddbara bibliotek som saknas i nya installationen. Du kan lĂ€gga till dessa itll nya installationen eller ta bort funktionerna som anvĂ€nder dem i gamla installationen. En lista med problembiblioteken finns i filen: %s kan inte köra pg_upgrade inifrĂ„n nya klusterdatakatalogen i Windows kontroll av "%s" misslyckades: %s kontroll av "%s" misslyckades: kan inte exekvera (rĂ€ttighet saknas) kontroll av "%s" misslyckades: kan inte lĂ€sa filen (rĂ€ttighet saknas) kontroll av "%s" misslyckades: inte en vanlig fil barnprocess avslutade felaktigt: status %d barnprocess avslutade felaktigt: %s kommandot för lĂ„ngt anslutning till databas misslyckades: %skopierar "%s" till "%s" kan inte sĂ€tta rĂ€ttigheten "körbar" pĂ„ filen "%s": %s kunde inte ansluta till kĂ€ll-postmaster som startats med kommandot: %s kunde inte ansluta till mĂ„l-postmaster som startats med kommandot: %s kunde inte skapa hĂ„rd lĂ€nk mellan gamla och nya datakatalogerna: %s I lĂ€nk-lĂ€ge mĂ„ste gamla och nya datakatalogerna vara i samma filsystem. kunde inte skapa arbetsprocess: %s kunde inte skapa arbetstrĂ„d: %s kunde inte ta bort katalog "%s" kunde inte bestĂ€mma aktuell katalog kunde inte bestĂ€mma antalet anvĂ€ndare kunde inte hĂ€mta kontrolldata med %s: %s kunde inte hĂ€mta datakatalogen med %s: %s kunde inte hĂ€mta pg_ctl versionsdata med %s: %s kunde inte lĂ€sa versionutdata för pg_ctl frĂ„n %s kunde inte ladda lĂ€nkbibliotek "%s": %skunde inte öppna fil "%s" för lĂ€sning: %s kan inte öppna fil "%s": %s kunde inte öppna versionsfil "%s" kunde inte tolka versionsfil "%s" kunde inte lĂ€sa rad %d frĂ„n fil "%s": %s kunde inte göra stat pĂ„ tablespace-katalog "%s": %s kunde inte skriva till loggfil: "%s" databasanvĂ€ndare "%s" Ă€r inte installationsanvĂ€ndaren kodning för databasen "%s" matchar inte: gammal "%s", ny "%s" fel vid kontroll av filexistens "%s.%s" ("%s" till "%s"): %s fel vid kopiering av relation "%s.%s" ("%s" till "%s"): %s fel vid kopiering av relation "%s.%s": kunde inte skapa filen "%s": %s fel vid kopiering av relation "%s.%s": kunde inte öppna filen "%s": %s fel vid kopiering av relation "%s.%s": kunde inte lĂ€sa filen "%s": %s fel vid kopiering av relation "%s.%s": kunde inte göra stat pĂ„ file "%s": %s fel vid kopiering av relation "%s.%s": kunde inte skriva filen "%s": %s fel vid kopiering av relation "%s.%s": partiell sida hittad i fil "%s" fel vid skapande av lĂ€nk för relation "%s.%s" ("%s" till "%s"): %s kör: %s misslyckades med att hĂ€mta systemlokalnamn för "%s" misslyckades med att hĂ€mta aktuell lokal misslyckades med att Ă„terstĂ€lla gamla lokalen "%s" fatalt ogiltigt nytt portnummer ogiltigt gammalt portnummer lc_collate-vĂ€rden för databasen "%s" matchar inte: gammal "%s", ny "%s" lc_ctype-vĂ€rden för databasen "%s" matchar inte: gammal "%s", ny "%s" libpq:s omgivningsvariabel %s har ett icke-lokalt servervĂ€rde: %s lĂ€nkar "%s" till "%s" avbildningar för databasen "%s": nya klusterbinĂ€rer Ă€r inya klusterdatan Ă€r ii klustret finns redan ny tablespace-katalog: "%s" notisokgamla och nya klustrets pg_controldata checksumversioner matchar inte gamla och nya pg_controldata WAL-blockstorlekar Ă€r ogiltiga eller matchar inte gamla och nya pg_controldata WAL-segmentstorlekar Ă€r ogiltiga eller matchar inte gamla och nya pg_controldata-alignments Ă€r ogiltiga eller matchar inte. Troligen Ă€r ett kluster en 32-bitars-installation och den andra 64-bitars gamla och nya pg_controldata-blockstorlekar Ă€r ogiltiga eller matchar inte gamla och nya pg_controldata datum/tid-lagringstyper matchar inte gamla och nya pg_controldata stora-objekt-chunkstorlekar Ă€r ogiltiga eller matchar inte gamla och nya pg_controldata maximal TOAST-chunkstorlek ogiltiga eller matchar inte gamla och nya pg_controldata maximal identifierarlĂ€ngder Ă€r ogiltiga eller matchar inte gamla och nya pg_controldata maxilmalt indexerade kolumner ogiltiga eller matchar inte gamla och nya pg_controldata maximala relationssegmentstorlekar Ă€r ogiltiga eller matchar inte gamla klusterbinĂ€rer Ă€r igamla klusterdatan Ă€r igamla klustret anvĂ€nder inte datachecksummor men nya gör det gamla klustret anvĂ€nder datachecksummor men nya gör inte det gamla databasen "%s" kan inte hittas i nya klustret slut pĂ„ minne pg_ctl misslyckades att start kĂ€llservern eller sĂ„ misslyckades anslutningen pg_ctl misslyckades att start mĂ„lservern eller sĂ„ misslyckades anslutningen pg_upgrade uppgraderar ett PostgreSQL-kluster till en annan major-version. relnamn: %s.%s: reloid: %u reltblutrymme: %s skriver om "%s" till "%s" tablespace-katalogen "%s" finns inte tablespace-sökvĂ€g "%s" Ă€r inte en katalog template0 fĂ„r inte tillĂ„ta anslutningar, dvs dess pg_database.datallowconn mĂ„ste vara false anvĂ€ndarangivet gammalt portnummer %hu korrigerat till %hu waitpid() misslyckades: %s varning