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
Þ•ó´KLxy| ˜Ï£hs]Üß:'-Bep#ÖSú^N ­ëÎEºå"÷ . B D ŸL :ì A'!;i!J¥!Eð!A6"Gx"AÀ"K#;N#SŠ#MÞ#J,$Ew$G½$@%¢F%é%û% &&4&M& j&!‹&­&Ì&%ç&) '7''U'}'™'®'$Ë'ð' ()(%F($l(‘(ª("¯(Ò(ë(î(ò()*)-I)ew)%Ý)B*OF*–*%°**Ö*5+7++Q+*}++¨+Ô+"ï++,+>,&j,J‘,RÜ,/-L-ài-"J.m.&.%´. Ú.è.7/;/6M/6„/$»/à/Ký/'I0Pq0PÂ0K19_1™1t)2 ž2<¨2bå2\H3?¥3å3.ü3++4W4Ep4¶45Ï4&5 ,54M55‚5*¸5ã52ÿ5626<i62¦66Ù6<7iM7i·7#!8EE88‹8MÄ8&999U9M]9[«9>:tF:…»:4A<v=@>Ñ?å@LëA8B:SB<ŽB*ËB#öBC!,CNC2dCD—CDÜC“!D$µD#ÚD þD&E(FE(oE*˜E/ÃE,óE F)@FjF ˆF(©F*ÒF-ýF!+G+MG>yGC¸G8üGE5HC{HC¿HCIDGIFŒIBÓIJ*%J!PJ"rJ•JœJµJFÎJDK?ZKšK°KÍKéKLBLGHLIL{ÚLCVM@šMPÛMQ,NR~NOÑNV!OxO”O=­O9ëO/%PUP?dP?¤PHäP+-QYQ)qQ(›QVÄQ3RORžWRöSùS TÇTfæTšMU|èU/eW0•WøÆW(¿ZgèZvP[Ç[æ\”é]v~_:õ`%0bVbsbb’bŸšbE:cO€cHÐcNdNhdM·dEeOKeD›eHàeV)fW€fNØfN'g[vgBÒg¢h¸hÍhâhóhi$,iQini$i²i/Ñi3j'5j9]j!—j¹jÊjåjkk:k&Wk&~k-¥kÓkØk÷klll+&l7RlAŠl´ÌlGmFÉmŸn°n.ÏnTþnBSo–o&²o%Ùo2ÿo2p+Kp$wpGœp$äpd qpnq)ßq) r3r45s$jsAs:Ñs t!$tEFtŒt?Ÿt?ßtHu)hua’uGôu_ŠŠ|É‹FŒ@^ŒNŸŒ2îŒ,!N$d)‰:³HîH7Ž«€Ž0,-]+‹-·&å: =GH…)Î&ø6‘"V‘ y‘5š‘9БR ’%]’Tƒ’^Ø’J7“9‚“M¼“J ”MU”X£”Jü”TG•Cœ•à•5ï•*%–+P–|–Ž–«–cÈ–a,—:Ž—)É—$ó—$˜=˜\˜H_˜I¨˜Iò˜<™E¼™OšSRšV¦šOýšRM›Y ›$ú›œv>œvµœR,I‘IÛd%ž+Šž0¶ž<çž<$Ÿ˜aŸ8úŸ3 ¸À/v šª³#f›\½±cŠ6ñV_ÂóTÙà®I¿RæBF<Cߌ¡˜`yŽrµG´·…dzi ¨òÚjÆNl¥‹>1♂”Í: –bœ~] o»'Ê^h3ä@ï2‘}ÁsqÃ?’Síܼ,žE&OŬð¶ÎJ‰­ÝLx¦{. K*Ïeu•ÓU„=ëÒ[Þ²º 95"×!nê8¹—¤‡Ä«†Ô ©(+áèYAƒÑPa-tÉ4¢ŸkpX°€ZMwmDì¯gØ£Õ|ãåÛ$“ˆHW§0éQçÖ¾)î;ÌÐ%ÈË7Ç *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 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 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 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: 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 hash indexesChecking for incompatible "jsonb" data typeChecking for incompatible "line" data typeChecking for invalid "unknown" user columnsChecking for large objectsChecking for prepared transactionsChecking for presence of required librariesChecking for reg* data types in user tablesChecking for roles starting with "pg_"Consult 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 and free space information are not transferred by pg_upgrade so, once you start the new server, consider running: %s 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 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 some required control information: The target cluster contains prepared transactions The target cluster contains roles starting with "pg_" The target cluster lacks some required control information: 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 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 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 PG_VERSION file from %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 residesokold 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 warningProject-Id-Version: pg_upgrade (PostgreSQL) 10 Report-Msgid-Bugs-To: pgsql-bugs@postgresql.org POT-Creation-Date: 2017-09-19 09:51+0900 PO-Revision-Date: 2017-09-19 10:29+0900 Last-Translator: Ioseph Kim Language-Team: Korean Language: ko MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=1; plural=0; *í´ëŸ¬ìŠ¤í„° 호환성* *실패* pg_upgrade ìž‘ì—… ì „ì— ë¨¼ì € 해야 í•  것들: 새 ë²„ì „ì˜ initdb 명령으로 새 ë°ì´í„°ë² ì´ìŠ¤ í´ëŸ¬ìŠ¤í„°ë¥¼ 만들고 옛 서버를 중지하고 새 ì„œë²„ë„ ì¤‘ì§€í•˜ì„¸ìš”. 사용예: pg_upgrade -d oldCluster/data -D newCluster/data -b oldCluster/bin -B newCluster/bin or 여기서 pg_upgrade ìž‘ì—…ì„ ì‹¤íŒ¨í•œë‹¤ë©´, ìž¬ì‹œë„ í•˜ê¸° ì „ì— ë¨¼ì € 새 í´ëŸ¬ìŠ¤í„°ë¥¼ 처ìŒë¶€í„° 다시 만들어 진행해야 합니다. 옛 버전으로 옛 í´ëŸ¬ìŠ¤í„°ë¥¼ 사용해서 서버를 실행하려면, %s/global/pg_control.old 파ì¼ì˜ ì´ë¦„ì„ ".old" 빼고 바꾸어 사용해야합니다. 업그레ì´ë“œë¥¼ "link" 모드로 했기 때문ì—, 한번ì´ë¼ë„ 새 ë²„ì „ì˜ ì„œë²„ê°€ ì´ í´ëŸ¬ìŠ¤í„°ë¥¼ ì´ìš©í•´ì„œ 실행ë˜ì—ˆë‹¤ë©´, ì´ íŒŒì¼ì´ ë” ì´ìƒ 안전하지 않기 때문입니다. 업그레ì´ë“œ 진행 중 ------------------ ë¬¸ì œì  ë³´ê³ : . 옛 í´ëŸ¬ìŠ¤í„°ëŠ” "plpython_call_handler" 함수가 "public" 스키마 ì•ˆì— ì •ì˜ ë˜ì–´ìžˆìŠµë‹ˆë‹¤. ì´ í•¨ìˆ˜ëŠ” "pg_catalog" 스키마 ì•ˆì— ìžˆì–´ì•¼í•©ë‹ˆë‹¤. psqlì—ì„œ ë‹¤ìŒ ëª…ë ¹ìœ¼ë¡œ ì´ í•¨ìˆ˜ì˜ ìœ„ì¹˜ë¥¼ 살펴 ë³¼ 수 있습니다: \df *.plpython_call_handler "public" 스키마 ì•ˆì— ì´ í•¨ìˆ˜ê°€ 있는 경우는 8.1 버전 ì´ì „ 버전ì´ì—ˆìŠµë‹ˆë‹¤. 업그레ì´ë“œ ìž‘ì—…ì„ ì •ìƒì ìœ¼ë¡œ 마치려면, 먼저 "plpython" 관련 ê°ì²´ë“¤ì„ 먼저 ëª¨ë‘ ì§€ìš°ê³ , 새 버전용 ëª¨ë“ˆì„ ì„¤ì¹˜í•´ì„œ 사용해야 합니다. ì´ ì‚­ì œ ìž‘ì—…ì€ ë‹¤ìŒê³¼ ê°™ì´ ì§„í–‰í•©ë‹ˆë‹¤: DROP FUNCTION public.plpython_call_handler() ì´ ìž‘ì—…ì€ ê´€ë ¨ 모든 ë°ì´í„°ë² ì´ìŠ¤ 단위로 진행ë˜ì–´ì•¼ 합니다. 업그레ì´ë“œ 완료 --------------- 경고: 새 ë°ì´í„° 디렉터리는 옛 ë°ì´í„° 디렉터리 ì•ˆì— ë‘˜ 수 없습니다, 예: %s 경고: ì‚¬ìš©ìž ì •ì˜ í…Œì´ë¸”스페ì´ìŠ¤ 위치를 ë°ì´í„° 디렉터리 ì•ˆì— ë‘˜ 수 없습니다, 예: %s pg_upgrade ìž‘ì—…ì€ ë‹¤ìŒ ë„¤ê°œì˜ ì˜µì…˜ ê°’ì€ ë°˜ë“œì‹œ 지정해야 함: 옛 ë°ì´í„° í´ëŸ¬ìŠ¤í„° 디렉터리 (-d DATADIR) 새 ë°ì´í„° í´ëŸ¬ìŠ¤í„° 디렉터리 (-D DATADIR) 옛 ë²„ì „ì˜ "bin" 디렉터리 (-b BINDIR) 새 ë²„ì „ì˜ "bin" 디렉터리 (-B BINDIR) 해당 ë°ì´í„°ë² ì´ìŠ¤ì—ì„œ 해쉬 ì¸ë±ìŠ¤ë¥¼ 사용하고 있습니다. 해쉬 ì¸ë±ìŠ¤ ìžë£Œêµ¬ì¡°ê°€ 새 버전ì—ì„œ 호환ë˜ì§€ 않습니다. 업그레ì´ë“œ í›„ì— í•´ë‹¹ ì¸ë±ìŠ¤ë“¤ì„ REINDEX 명령으로 다시 만들어야 합니다. 해당 ë°ì´í„°ë² ì´ìŠ¤ì—ì„œ 해쉬 ì¸ë±ìŠ¤ë¥¼ 사용하고 있습니다. 해쉬 ì¸ë±ìŠ¤ ìžë£Œêµ¬ì¡°ê°€ 새 버전ì—ì„œ 호환ë˜ì§€ 않습니다. 업그레ì´ë“œ 후 ë‹¤ìŒ íŒŒì¼ì„ 슈í¼ìœ ì € 권한으로 실행한 psqlì—ì„œ 실행해서, REINDEX ìž‘ì—…ì„ ì§„í–‰í•˜ì„¸ìš”: %s ì´ ìž‘ì—…ì´ ìžˆê¸° 전까지는 해당 ì¸ë±ìŠ¤ëŠ” invalid ìƒíƒœë¡œ 사용할 수 없게 ë©ë‹ˆë‹¤. ì´ ë°ì´í„°ë² ì´ìŠ¤ëŠ” 대형 ê°ì²´ë¥¼ 사용하고 있습니다. 새 ë°ì´í„°ë² ì´ìŠ¤ì—서는 ì´ë“¤ì˜ ì ‘ê·¼ 권한 제어를 위해 추가ì ì¸ í…Œì´ë¸”ì„ ì‚¬ìš©í•©ë‹ˆë‹¤. 그래서 ì´ë“¤ì˜ ì ‘ê·¼ ê¶Œí•œì„ ê¸°ë³¸ê°’ìœ¼ë¡œ 설정하려면, %s 파ì¼ì„ 새 서버가 실행 ë˜ì—ˆì„ ë•Œ 슈í¼ìœ ì € 권한으로 psql 명령으로 실행 하세요. ì´ ë°ì´í„°ë² ì´ìŠ¤ëŠ” 대형 ê°ì²´ë¥¼ 사용하고 있습니다. 새 ë°ì´í„°ë² ì´ìŠ¤ì—서는 ì´ë“¤ì˜ ì ‘ê·¼ 권한 제어를 위해 추가ì ì¸ í…Œì´ë¸”ì„ ì‚¬ìš©í•©ë‹ˆë‹¤. 업그레ì´ë“œ 후 ì´ ê°ì²´ë“¤ì˜ ì ‘ê·¼ ê¶Œí•œì€ pg_largeobject_metadata í…Œì´ë¸”ì— ê¸°ë³¸ê°’ìœ¼ë¡œ 지정ë©ë‹ˆë‹¤. ë°ì´í„°ë² ì´ìŠ¤ ì—°ê²° 실패: %s ì›ë³¸ ë°ì´í„°ë² ì´ìŠ¤: ëŒ€ìƒ ë°ì´í„°ë² ì´ìŠ¤: %s $ export PGDATAOLD=oldCluster/data $ export PGDATANEW=newCluster/data $ export PGBINOLD=oldCluster/bin $ export PGBINNEW=newCluster/bin $ pg_upgrade -?, --help ì´ ë„움ë§ì„ 보여주고 마침 -B, --new-bindir=BINDIR 새 í´ëŸ¬ìŠ¤í„° 실행 파ì¼ì˜ 디렉터리 -D, --new-datadir=DATADIR 새 í´ëŸ¬ìŠ¤í„° ë°ì´í„° 디렉터리 -O, --new-options=옵션 새 서버ì—ì„œ 사용할 서버 옵션들 -P, --new-port=PORT 새 í´ëŸ¬ìŠ¤í„° í¬íŠ¸ 번호 (기본값 %d) -U, --username=ì´ë¦„ í´ëŸ¬ìŠ¤í„° 슈í¼ìœ ì € (기본값 "%s") -V, --version 버전 정보를 보여주고 마침 -b, --old-bindir=BINDIR 옛 í´ëŸ¬ìŠ¤í„° 실행 파ì¼ì˜ 디렉터리 -c, --check 실 ìž‘ì—… ì—†ì´, 그냥 검사만 -d, --old-datadir=DATADIR 옛 í´ëŸ¬ìŠ¤í„° ë°ì´í„° 디렉터리 -j, --jobs ë™ì‹œì— ìž‘ì—…í•  프로세스 ë˜ëŠ” 쓰레드 수 -k, --link 새 í´ëŸ¬ìŠ¤í„° êµ¬ì¶•ì„ ë³µì‚¬ 대신 ë§í¬ 사용 -o, --old-options=옵션 옛 서버ì—ì„œ 사용할 서버 옵션들 -p, --old-port=PORT 옛 í´ëŸ¬ìŠ¤í„° í¬íŠ¸ 번호 (기본값 %d) -r, --retain ìž‘ì—… 완료 후 ì‚¬ìš©í–ˆë˜ SQLê³¼ 로그 íŒŒì¼ ë‚¨ê¹€ -v, --verbose ìž‘ì—… ë‚´ì—­ì„ ìžì„¸ížˆ 남김 C:\> set PGDATAOLD=oldCluster/data C:\> set PGDATANEW=newCluster/data C:\> set PGBINOLD=oldCluster/bin C:\> set PGBINNEW=newCluster/bin C:\> pg_upgrade WAL ë¸”ë¡ í¬ê¸° WAL ì¡°ê° í¬ê¸° ë¸”ë¡ í¬ê¸° ì²´í¬í¬ì¸íŠ¸ ë‹¤ìŒ XID ìžë£Œ ì²´í¬ì„¬ 버전 date/time ìžë£Œí˜•ì„ 정수로? 리셋 ë’¤ 첫 WAL ì¡°ê° float8 ì¸ìž 처리 ë°©ì‹ ëŒ€í˜• 릴레ì´ì…˜ ì¡°ê° í¬ê¸° 대형 ê°ì²´ ì¡°ê° í¬ê¸° 마지막 ì²´í¬í¬ì¸íŠ¸ ë‹¤ìŒ MultiXactId 마지막 ì²´í¬í¬ì¸íŠ¸ ë‹¤ìŒ MultiXactOffset 마지막 ì²´í¬í¬ì¸íŠ¸ ë‹¤ìŒ OID 마지막 ì²´í¬í¬ì¸íŠ¸ ì œì¼ ì˜¤ëž˜ëœ MultiXactId 최대 토스트 ì¡°ê° í¬ê¸° 최대 ì •ë ¬ 최대 ì‹ë³„ìž ê¸¸ì´ ìµœëŒ€ ì¸ë±ìŠ¤ 칼럼 수 pg_upgrade [옵션]... 해당 ì¸ë±ìŠ¤: "%s.%s" 해당 ì¸ë±ìŠ¤ì˜ OID: %u "%s.%s" ê°ì²´ì˜ 토스트 í…Œì´ë¸” 해당 토스트 ë² ì´ë¸”ì˜ OID: %u"%s" 파ì¼ì€ 디렉터리가 아닙니다. %-*s%d: controldata ë³µì› ë¬¸ì œ %d: pg_resetwal 문제 %s%s %s.%s: %u / %u %s: root 권한으로 실행할 수 ì—†ìŒ %s: 실행할 í”„ë¡œê·¸ëž¨ì„ ì°¾ì„ ìˆ˜ 없습니다. 옛 global/pg_control 파ì¼ì— ".old" ì´ë¦„ì„ ë§ë¶™ìž…니다.template0 ë°ì´í„°ë² ì´ìŠ¤ë¥¼ 제외한 다른 모든 ë°ì´í„°ë² ì´ìŠ¤ëŠ” ì ‘ì†ì´ 가능해야합니다. 예: ê·¸ë“¤ì˜ pg_database.datallowconn ê°’ì€ true여야 합니다. 새 í´ëŸ¬ìŠ¤í„°ì˜ 모든 ë¡œìš°ì— ëŒ€í•´ì„œ 통계 ì •ë³´ 수집 중필요한 컨트롤 ì •ë³´ ì—†ì´ëŠ” 진행할 수 ì—†ìŒ, 중지 함 ì‚¬ìš©ìž ì •ì˜ í…Œì´ë¸”스페ì´ìŠ¤ë¥¼ 사용하는 경우 ê°™ì€ ì‹œìŠ¤í…œ 카탈로그 버전으로 업그레ì´ë“œ ìž‘ì—…ì„ ì§„í–‰í•  수 없습니다. í´ëŸ¬ìŠ¤í„° 버전 검사 중ë°ì´í„°ë² ì´ìŠ¤ ì—°ê²° ì„¤ì •ì„ í™•ì¸ ì¤‘ë°ì´í„°ë² ì´ìŠ¤ 사용ìžê°€ 설치 ìž‘ì—…ì„ í•œ 사용ìžì¸ì§€ 확ì¸í•©ë‹ˆë‹¤contrib/isn ëª¨ë“ˆì˜ bigint 처리가 서로 ê°™ì€ì§€ í™•ì¸ ì¤‘í•´ì‰¬ ì¸ë±ìŠ¤ í™•ì¸ ì¤‘"jsonb" ìžë£Œí˜• 호환성 í™•ì¸ ì¤‘"line" ìžë£Œí˜• 호환성 í™•ì¸ ì¤‘ìž˜ëª»ëœ "unknown" ì‚¬ìš©ìž ì¹¼ëŸ¼ì„ í™•ì¸ ì¤‘ëŒ€í˜• ê°ì²´ í™•ì¸ ì¤‘ë¯¸ë¦¬ ì¤€ë¹„ëœ íŠ¸ëžœìž­ì…˜ì„ í™•ì¸ ì¤‘í•„ìš”í•œ ë¼ì´ë¸ŒëŸ¬ë¦¬ í™•ì¸ ì¤‘ì‚¬ìš©ìžê°€ 만든 í…Œì´ë¸”ì— reg* ìžë£Œí˜•ì„ 쓰는지 í™•ì¸ ì¤‘"pg_"ë¡œ 시작하는 롤 í™•ì¸ ì¤‘"%s" 파ì¼ì˜ 마지막 ë¶€ë¶„ì„ ì‚´íŽ´ë³´ë©´ ì´ ë¬¸ì œë¥¼ í’€ 실마리가 ë³´ì¼ ê²ƒìž…ë‹ˆë‹¤. "%s" ë˜ëŠ” "%s" 파ì¼ì˜ 마지막 ë¶€ë¶„ì„ ì‚´íŽ´ë³´ë©´ ì´ ë¬¸ì œë¥¼ í’€ 실마리가 ë³´ì¼ ê²ƒìž…ë‹ˆë‹¤. 옛 %s ê°ì²´ë¥¼ 새 서버로 복사 ì¤‘ì‚¬ìš©ìž ë¦´ë ˆì´ì…˜ íŒŒì¼ ë³µì‚¬ 중 옛 í´ëŸ¬ìŠ¤í„° ìžë£Œ 파ì¼ì„ 지우는 스í¬ë¦½íŠ¸ë¥¼ 만들지 못했습니다. ì‚¬ìš©ìž ì •ì˜ í…Œì´ë¸”스페ì´ìŠ¤ë‚˜, 새 í´ëŸ¬ìŠ¤í„°ê°€ 옛 í´ëŸ¬ìŠ¤í„° ì•ˆì— ìžˆê¸° 때문입니다. 옛 í´ëŸ¬ìŠ¤í„° ìžë£ŒëŠ” ì§ì ‘ 찾아서 지우세요. ë°ì´í„°ë² ì´ìŠ¤ 스키마 ë¤í”„를 만듭니다 ì „ì—­ ê°ì²´ ë¤í”„를 만듭니다새 í´ëŸ¬ìŠ¤í„° 통계정보 수집 스í¬ë¦½íŠ¸ë¥¼ 만듭니다옛 í´ëŸ¬ìŠ¤í„°ë¥¼ 지우는 스í¬ë¦½íŠ¸ë¥¼ 만듭니다ë°ì´í„°ë² ì´ìŠ¤: %s 새 %sì—ì„œ íŒŒì¼ ì§€ìš°ëŠ” 중"%s" ë°ì´í„°ë² ì´ìŠ¤ ë‚´ í…Œì´ë¸” ì´ë¦„ì´ ì„œë¡œ 다릅니다: 실패, 종료함 ì›ë³¸ í´ëŸ¬ìŠ¤í„°ìš© 실 ë°ì´í„° 디렉터리를 찾는 ì¤‘ëŒ€ìƒ í´ëŸ¬ìŠ¤í„°ìš© 실 ë°ì´í„° 디렉터리를 찾는 중새 í´ëŸ¬ìŠ¤í„°ì˜ 모든 ë¡œìš°ì— ëŒ€í•´ì„œ ì˜êµ¬ 격리(freeze) ì¤‘ì‚¬ìš©ìž ë¦´ë ˆì´ì…˜ íŒŒì¼ ë§í¬ 중 새 í´ëŸ¬ìŠ¤í„° ìžë£Œì™€ ì‹¤í–‰íŒŒì¼ ë””ë ‰í„°ë¦¬ê°€ 서로 ë©”ì´ì ¸ ë²„ì „ì´ ë‹¤ë¦…ë‹ˆë‹¤. "%s" 새 ë°ì´í„°ë² ì´ìŠ¤ í´ëŸ¬ìŠ¤í„°ê°€ 비어있지 않습니다. 옛 í´ëŸ¬ìŠ¤í„°ì˜ %u OID (해당 ë°ì´í„°ë² ì´ìŠ¤: "%s")ê°€ 새 í´ëŸ¬ìŠ¤í„°ì— ì—†ìŒ: %s 새 í´ëŸ¬ìŠ¤í„°ì˜ %u OID (해당 ë°ì´í„°ë² ì´ìŠ¤: "%s")ê°€ 옛 í´ëŸ¬ìŠ¤í„°ì— ì—†ìŒ: %s 옛 í´ëŸ¬ìŠ¤í„° ìžë£Œì™€ ì‹¤í–‰íŒŒì¼ ë””ë ‰í„°ë¦¬ê°€ 서로 ë©”ì´ì ¸ ë²„ì „ì´ ë‹¤ë¦…ë‹ˆë‹¤. 새 í´ëŸ¬ìŠ¤í„°ì—서만 설치 사용 사용ìžê°€ ì •ì˜ë  수 ìžˆìŒ pg_upgrade 작업으로는 통계 정보와 빈 공간 정보는 업그레ì´ë“œ ë˜ì§€ 않습니다. 새 서버가 실행 ë  ë•Œ, ë‹¤ìŒ ëª…ë ¹ì„ ìˆ˜í–‰í•˜ê¸¸ 권합니다: %s pg_upgrade ìž‘ì—…ì—서는 최ì í™”기를 위한 통계 정보까지 업그레ì´ë“œ 하지는 않습니다. 새 서버가 실행 ë  ë•Œ, ë‹¤ìŒ ëª…ë ¹ì„ ìˆ˜í–‰í•˜ê¸¸ 권합니다: %s 옵션: ì¼ê´€ì„± 검사 수행중 ------------------ 옛 ìš´ì˜ ì„œë²„ì—ì„œ ì¼ê´€ì„± 검사를 진행합니다. ------------------------------------------ %u OIDì— ëŒ€í•œ "%s" ë°ì´í„°ë² ì´ìŠ¤ ì´ë¦„ì´ ì„œë¡œ 다릅니다: 옛 ì´ë¦„: "%s.%s", 새 ì´ë¦„: "%s.%s" 옛 í´ëŸ¬ìŠ¤í„°ì—ì„œ 문제가 있는 í•¨ìˆ˜ë“¤ì„ ì‚­ì œí•˜ê³  진행하세요. WAL ì•„ì¹´ì´ë¸Œ 재설정 중새 í´ëŸ¬ìŠ¤í„°ì— ë°ì´í„°ë² ì´ìŠ¤ 스키마 ë³µì› ì¤‘ 새 í´ëŸ¬ìŠ¤í„°ì— ì „ì—­ ê°ì²´ë¥¼ ë³µì› ì¤‘ìž‘ì—… ë‚´ì—­ì„ ìžì„¸ížˆ ë´„ 아래 스í¬ë¦½íŠ¸ë¥¼ 실행하면, 옛 í´ëŸ¬ìŠ¤í„° ìžë£Œë¥¼ 지울 것입니다: %s SQL 명령 실패 %s %s새 í´ëŸ¬ìŠ¤í„°ì—ì„œ frozenxid, minmxid ê°’ 설정 중새 í´ëŸ¬ìŠ¤í„°ì—ì„œ minmxid ê°’ 설정 중새 í´ëŸ¬ìŠ¤í„°ìš© ë‹¤ìŒ OID 설정 중새 í´ëŸ¬ìŠ¤í„°ìš© ë‹¤ìŒ ë©€í‹° 트랜잭션 ID와 위치 ê°’ 설정 중새 í´ëŸ¬ìŠ¤í„°ìš© ë‹¤ìŒ íŠ¸ëžœìž­ì…˜ ID와 epoch ê°’ 설정 중새 í´ëŸ¬ìŠ¤í„°ìš© ì œì¼ ì˜¤ëž˜ëœ ë©€í‹° 트랜잭션 ID 설정 중ë°ì´í„° 디렉터리 fsync ìž‘ì—… 중옛 í´ëŸ¬ìŠ¤í„°ì— 미리 ì¤€ë¹„ëœ íŠ¸ëžœìž­ì…˜ì´ ìžˆìŒ ì˜› í´ëŸ¬ìŠ¤í„°ì— "pg_" 시작하는 ë¡¤ì´ ìžˆìŠµë‹ˆë‹¤. 옛 í´ëŸ¬ìŠ¤í„°ì— 필요한 컨트롤 ì •ë³´ê°€ 몇몇 빠져있ìŒ: 새 í´ëŸ¬ìŠ¤í„°ì— 미리 ì¤€ë¹„ëœ íŠ¸ëžœìž­ì…˜ì´ ìžˆìŒ ìƒˆ í´ëŸ¬ìŠ¤í„°ì— "pg_"ë¡œ 시작하는 ë¡¤ì´ ìžˆìŠµë‹ˆë‹¤. 새 í´ëŸ¬ìŠ¤í„°ì— 필요한 컨트롤 ì •ë³´ê°€ 몇몇 빠져있ìŒ: 새 서버가 현재 ìš´ì˜ ë˜ê³  있습니다. 먼저 서버를 중지하고 진행하세요. 옛 서버가 현재 ìš´ì˜ ë˜ê³  있습니다. 먼저 서버를 중지하고 진행하세요. "%s" 실행ì—ì„œ 문제 ë°œìƒ ì´ ë„구는 PostgreSQL 8.4 ì´ìƒ 버전ì—ì„œ 사용할 수 있습니다. ì´ ë„구는 PostgreSQL %s 버전으로만 업그레ì´ë“œ í•  수 있습니다. ì´ ë„구는 ë” ë‚®ì€ ë©”ì´ì ¸ PostgreSQL 버전으로 다운그레ì´ë“œí•˜ëŠ”ë° ì‚¬ìš©í•  수 없습니다. 보다 ìžì„¸í•œ ì‚¬ìš©ë²•ì€ "%s --help" ëª…ë ¹ì„ ì´ìš©í•˜ì„¸ìš”. %s ì´ë¦„ì„ %s ì´ë¦„으로 바꿀 수 ì—†ìŒ. 사용법: ìš´ì˜ ì„œë²„ 검사를 í•  때는, 옛 서버, 새 ì„œë²„ì˜ í¬íŠ¸ë¥¼ 다르게 지정해야 합니다. 옛 서버가 9.1 버전 ì´ì „ ì´ë¼ë©´ 옛 ì„œë²„ì˜ í¬íŠ¸ë¥¼ 반드시 지정해야 합니다. 현재 ë””ë ‰í„°ë¦¬ì˜ ì½ê¸° 쓰기 ê¶Œí•œì„ ë¶€ì—¬í•˜ì„¸ìš”. %s ìœ„ì¹˜ì˜ ë””ë ‰í„°ë¦¬ë¥¼ 알고 있어야 함. %s 명령행 옵션ì´ë‚˜, %s 환경 변수를 사용하세요. 설치ë˜ì–´ 있는 "contrib/isn" ëª¨ë“ˆì€ bigint ìžë£Œí˜•ì„ 사용합니다. ì´ bigint ìžë£Œí˜•ì˜ 처리 ë°©ì‹ì´ 새 버전과 옛 버전 ì‚¬ì´ í˜¸í™˜ì„±ì´ ì—†ìŠµë‹ˆë‹¤. ì´ ëª¨ë“ˆì„ ê³„ì† ì‚¬ìš©í•˜ë ¤ë©´, 사용ìžê°€ ì§ì ‘ 업그레ì´ë“œ 해야 합니다. 먼저 옛 버전ì—ì„œ "contrib/isn" ëª¨ë“ˆì„ ì‚­ì œí•˜ê³  서버를 재실행하고, 업그레ì´ë“œ í•œ ë’¤ ì§ì ‘ 나머지 ìž‘ì—…ì„ ì§„í–‰í•˜ì‹­ì‹œì˜¤. 문제가 있는 함수는 아래 íŒŒì¼ ì•ˆì— ìžˆìŠµë‹ˆë‹¤: %s 옛 ì„œë²„ì˜ ì‚¬ìš©ìžê°€ 만든 í…Œì´ë¸”ì—ì„œ reg* ìžë£Œí˜•ì„ 사용하고 있습니다. ì´ ìžë£Œí˜•ë“¤ì€ pg_upgrade 명령으로 ë‚´ì •ëœ ì‹œìŠ¤í…œ OID를 사용하지 못할 수 있습니다. 그래서 업그레ì´ë“œ ìž‘ì—…ì„ ì§„í–‰í•  수 없습니다. 사용하고 있는 í…Œì´ë¸”ë“¤ì„ ì§€ìš°ê³  업그레ì´ë“œ ìž‘ì—…ì„ ë‹¤ì‹œ ì‹œë„하세요. ì´ëŸ° ìžë£Œí˜•ì„ 사용하는 파ì¼ì€ ë‹¤ìŒ íŒŒì¼ë“¤ 입니다: %s ì‚¬ìš©ìž í…Œì´ë¸”ì—ì„œ "jsonb" ìžë£Œí˜•ì„ 사용하고 있습니다. 9.4 베타 비전 ì´í›„ JSONB 내부 ìžë£Œ 구조가 바뀌었습니다. 그래서, 업그레ì´ë“œ ìž‘ì—…ì´ ë¶ˆê°€ëŠ¥í•©ë‹ˆë‹¤. 해당 í…Œì´ë¸”ë“¤ì„ ì§€ìš°ê³  업그레ì´ë“œ ìž‘ì—…ì„ ì§„í–‰í•˜ì„¸ìš” 해당 ìžë£Œí˜•ì„ 쓰는 파ì¼ì€ 다ìŒê³¼ 같습니다: %s 해당 ë°ì´í„°ë² ì´ìŠ¤ì—ì„œ "line" ìžë£Œí˜•ì„ 사용하는 ì¹¼ëŸ¼ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ìžë£Œí˜•ì˜ 입출력 ë°©ì‹ì´ 옛 버전과 새 버전ì—ì„œ 서로 호환하지 않습니다. 먼저 ì´ ìžë£Œí˜•ì„ 사용하는 í…Œì´ë¸”ì„ ì‚­ì œ 후 업그레ì´ë“œ ìž‘ì—…ì„ í•˜ê³ , 수ë™ìœ¼ë¡œ ë³µì› ìž‘ì—…ì„ í•´ì•¼ 합니다. 해당 파ì¼ë“¤ì€ 다ìŒê³¼ 같습니다: %s 해당 ë°ì´í„°ë² ì´ìŠ¤ì—ì„œ ì‚¬ìš©ìž í…Œì´ë¸”ì—ì„œ "unknown" ìžë£Œí˜•ì„ 사용하고 있습니다. ì´ ìžë£Œí˜•ì€ ë” ì´ìƒ 사용할 수 없습니다. ì´ ë¬¸ì œë¥¼ 옛 버전ì—ì„œ 먼저 정리하고 업그레ì´ë“œ ìž‘ì—…ì„ ì§„í–‰í•˜ì„¸ìš”. 해당 파ì¼ì€ 다ìŒê³¼ 같습니다: %s 옛 버전ì—는 있고, 새 버전ì—는 없는 ë¼ì´ë¸ŒëŸ¬ë¦¬ë“¤ì´ 있습니다. 새 ë²„ì „ì— í•´ë‹¹ ë¼ì´ë¸ŒëŸ¬ë¦¬ë“¤ì„ 설치하거나, 옛 버전ì—ì„œ 해당 ë¼ì´ë¸ŒëŸ¬ë¦¬ë¥¼ 삭제하고, 업그레ì´ë“œ ìž‘ì—…ì„ í•´ì•¼í•©ë‹ˆë‹¤. 문제가 있는 ë¼ì´ë¸ŒëŸ¬ë¦¬ë“¤ì€ 다ìŒê³¼ 같습니다: %s 윈ë„우즈 환경ì—서는 pg_upgrade ëª…ë ¹ì€ ìƒˆ í´ëŸ¬ìŠ¤í„° ë°ì´í„° 디렉터리 안ì—서는 실행할 수 ì—†ìŒ "%s" 검사 실패: %s "%s" 검사 실패: 실행할 수 ì—†ìŒ (ì ‘ê·¼ 권한 ì—†ìŒ) "%s" 검사 실패: 해당 파ì¼ì„ ì½ì„ 수 ì—†ìŒ (ì ‘ê·¼ 권한 ì—†ìŒ) "%s" 검사 실패: ì¼ë°˜ 파ì¼ì´ 아닙니다 하위 ìž‘ì—…ìžê°€ ë¹„ì •ìƒ ì¢…ë£Œë¨: %s ëª…ë ¹ì´ ë„ˆë¬´ 긺 ë°ì´í„°ë² ì´ìŠ¤ ì—°ê²° 실패: %s"%s" ê°ì²´ë¥¼ "%s" ê°ì²´ë¡œ 복사 중 "%s" 파ì¼ì— 실행 ê¶Œí•œì„ ì¶”ê°€ í•  수 ì—†ìŒ: %s ë‹¤ìŒ ëª…ë ¹ìœ¼ë¡œ ì‹¤í–‰ëœ ì›ë³¸ 서버로 ì ‘ì†í•  수 ì—†ìŒ: %s ë‹¤ìŒ ëª…ë ¹ìœ¼ë¡œ ì‹¤í–‰ëœ ëŒ€ìƒ ì„œë²„ë¡œ ì ‘ì†í•  수 ì—†ìŒ: %s ë°ì´í„° 디렉터리간 하드 ë§í¬ë¥¼ 만들 수 ì—†ìŒ: %s 하드 ë§í¬ë¥¼ 사용하려면, ë‘ ë””ë ‰í„°ë¦¬ê°€ ê°™ì€ ì‹œìŠ¤í…œ 볼륨 ì•ˆì— ìžˆì–´ì•¼ 합니다. ìž‘ì—…ìš© 프로세스를 만들 수 ì—†ìŒ: %s ìž‘ì—…ìš© 쓰레드를 만들 수 ì—†ìŒ: %s "%s" 디렉터리를 ì‚­ì œ í•  수 ì—†ìŒ í˜„ìž¬ 디렉터리 위치를 ì•Œ 수 ì—†ìŒ ì‚¬ìš©ìž ìˆ˜ë¥¼ 확ì¸í•  수 ì—†ìŒ %s 사용하는 컨트롤 ìžë£Œë¥¼ 구할 수 ì—†ìŒ: %s %s 지정한 ë°ì´í„° 디렉터리를 ì°¾ì„ ìˆ˜ ì—†ìŒ: %s %s ëª…ë ¹ì„ ì‚¬ìš©í•´ì„œ pg_ctl 버전 ìžë£Œë¥¼ 구할 수 ì—†ìŒ: %s %sì—ì„œ pg_ctl ë²„ì „ì„ ì•Œ 수 ì—†ìŒ "%s" ë¼ì´ë¸ŒëŸ¬ë¦¬ 로드 실패: %s"%s" 파ì¼ì„ ì½ê¸° 위해 ì—´ 수 없습니다: %s "%s" 파ì¼ì„ ì—´ 수 ì—†ìŒ: %s 버전 íŒŒì¼ ì—´ê¸° 실패: %s "%s" 파ì¼ì—ì„œ PG_VERSIONì„ í•´ì„í•  수 ì—†ìŒ %d 번째 ì¤„ì„ "%s" 파ì¼ì—ì„œ ì½ì„ 수 ì—†ìŒ: %s "%s" í…Œì´ë¸”스페ì´ìŠ¤ ë””ë ‰í„°ë¦¬ì˜ ìƒíƒœ 정보를 구할 수 ì—†ìŒ: %s "%s" 로그 파ì¼ì„ 쓸 수 ì—†ìŒ "%s" ë°ì´í„°ë² ì´ìŠ¤ 사용ìžëŠ” 설치 ìž‘ì—…ì„ í•œ 사용ìžê°€ 아닙니다 "%s" ë°ì´í„°ë² ì´ìŠ¤ì˜ ì¸ì½”ë”©ì´ ì„œë¡œ 다릅니다: 옛 서버 "%s", 새 서버 "%s" "%s.%s" ("%s" / "%s") 파ì¼ì´ 있는지 í™•ì¸ ë„중 오류 ë°œìƒ: %s "%s.%s" ("%s" / "%s") 릴레ì´ì…˜ 복사 중 오류: %s "%s.%s" 릴레ì´ì…˜ 복사 중 오류: "%s" 파ì¼ì„ 만들 수 ì—†ìŒ: %s "%s.%s" 릴레ì´ì…˜ 복사 중 오류: "%s" 파ì¼ì„ ì—´ 수 ì—†ìŒ: %s "%s.%s" 릴레ì´ì…˜ 복사 중 오류: "%s" 파ì¼ì„ ì½ì„ 수 ì—†ìŒ: %s "%s.%s" 릴레ì´ì…˜ 복사 중 오류: "%s" íŒŒì¼ ìƒíƒœ 정보를 ì•Œ 수 ì—†ìŒ: %s "%s.%s" 릴레ì´ì…˜ 복사 중 오류: "%s" 파ì¼ì„ 쓸 수 ì—†ìŒ: %s "%s.%s" 릴레ì´ì…˜ 복사 중 오류: "%s" 파ì¼ì— 페ì´ì§€ê°€ ì†ìƒë˜ì—ˆìŒ "%s.%s" ("%s" / "%s") 릴레ì´ì…˜ ë§í¬ 만드는 중 오류: %s 실행중: %s "%s"ìš© 시스템 ë¡œì¼€ì¼ ì´ë¦„ì„ ì•Œ 수 ì—†ìŒ í˜„ìž¬ 로케ì¼ì„ í™•ì¸ í•  수 ì—†ìŒ "%s" 옛 로케ì¼ì„ ë³µì›í•  수 ì—†ìŒ ì¹˜ëª…ì  ì˜¤ë¥˜ ìž˜ëª»ëœ ìƒˆ í¬íŠ¸ 번호 ìž˜ëª»ëœ ì˜› í¬íŠ¸ 번호 "%s" ë°ì´í„°ë² ì´ìŠ¤ì˜ lc_collate ê°’ì´ ì„œë¡œ 다릅니다: 옛 서버 "%s", 새 서버 "%s" "%s" ë°ì´í„°ë² ì´ìŠ¤ì˜ lc_ctype ê°’ì´ ì„œë¡œ 다릅니다: 옛 서버 "%s", 새 서버 "%s" %s libpq 환경 변수가 로컬 서버 ê°’ì´ ì•„ë‹˜: %s "%s" ê°ì²´ë¥¼ "%s" ê°ì²´ë¡œ ë§í¬ 중 "%s" ë°ì´í„°ë² ì´ìŠ¤ 맵핑 중: 새 í´ëŸ¬ìŠ¤í„° ì‹¤íŒ½íŒŒì¼ ìœ„ì¹˜ìƒˆ í´ëŸ¬ìŠ¤í„° ìžë£Œ 위치okí´ëŸ¬ìŠ¤í„°ê°„ pg_controldata ì²´í¬ì„¬ ë²„ì „ì´ ì„œë¡œ 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata WAL ë¸”ë¡ í¬ê¸°ê°€ 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata WAL ì¡°ê° í¬ê¸°ê°€ 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata ì •ë ¬ì´ ì„œë¡œ 다릅니다. 하나는 32비트고, 하나는 64ë¹„íŠ¸ì¸ ê²½ìš° 같습니다 í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata ë¸”ë¡ í¬ê¸°ê°€ 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata date/time 저장 í¬ê¸°ê°€ 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata 대형 ê°ì²´ ì¡°ê° í¬ê¸°ê°€ 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata 최대 토스트 ì¡°ê° í¬ê¸°ê°€ 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata 최대 ì‹ë³„ìž ê¸¸ì´ê°€ 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata 최대 ì¸ë±ìŠ¤ 칼럼수가 서로 다릅니다. í´ëŸ¬ìŠ¤í„°ê°„ pg_controldata 최대 릴레ì´ì…˜ ì¡°ê° í¬ê°€ê°€ 서로 다릅니다. 옛 í´ëŸ¬ìŠ¤í„° ì‹¤í–‰íŒŒì¼ ìœ„ì¹˜ì˜› í´ëŸ¬ìŠ¤í„° ìžë£Œ 위치옛 í´ëŸ¬ìŠ¤í„°ëŠ” ë°ì´í„° ì²´í¬ì„¬ ê¸°ëŠ¥ì„ ì‚¬ìš©í•˜ì§€ ì•Šê³ , 새 í´ëŸ¬ìŠ¤í„°ëŠ” 사용하고 있습니다. 옛 í´ëŸ¬ìŠ¤í„°ëŠ” ë°ì´í„° ì²´í¬ì„¬ ê¸°ëŠ¥ì„ ì‚¬ìš©í•˜ê³ , 새 í´ëŸ¬ìŠ¤í„°ëŠ” 사용하고 있지 않습니다. "%s" ì´ë¦„ì˜ ì˜› ë°ì´í„°ë² ì´ìŠ¤ë¥¼ 새 í´ëŸ¬ìŠ¤í„°ì—ì„œ ì°¾ì„ ìˆ˜ ì—†ìŒ ë©”ëª¨ë¦¬ 부족 ì›ë³¸ 서버를 실행하는 pg_ctl ìž‘ì—… 실패, ë˜ëŠ” ì—°ê²° 실패 ëŒ€ìƒ ì„œë²„ë¥¼ 실행하는 pg_ctl ìž‘ì—… 실패, ë˜ëŠ” ì—°ê²° 실패 새 ë°ì´í„° í´ëŸ¬ìŠ¤í„° 버전과 pg_upgrade ë²„ì „ì˜ ë©”ì´ì € ë²„ì „ì´ ì„œë¡œ 다릅니다. relname: %s.%s: reloid: %u reltblspace: %s "%s" ê°ì²´ë¥¼ "%s" ê°ì²´ë¡œ 다시 쓰는 중 "%s" ì´ë¦„ì˜ í…Œì´ë¸”스페ì´ìŠ¤ 디렉터리가 ì—†ìŒ "%s" í…Œì´ë¸”스페ì´ìŠ¤ 경로는 디렉터리가 아님 template0 ë°ì´í„°ë² ì´ìŠ¤ ì ‘ì†ì„ 금지해야 합니다. 예: 해당 ë°ì´í„°ë² ì´ìŠ¤ì˜ pg_database.datallowconn ê°’ì´ false여야 합니다. 지정한 %hu 옛 í¬íŠ¸ 번호를 %hu 번호로 바꿈 ê²½ê³