🔐 Sid Gifari File Manager Pro
v8.0.5 | 2026-06-14 16:13:33 | PHP 8.1.34
📂
/ (Root)
/
usr
/
share
/
locale
/
zh_CN
/
LC_MESSAGES
📍 /usr/share/locale/zh_CN/LC_MESSAGES
🔄 Refresh
✏️
Editing: pg_upgrade-13.mo
Read Only
�� \ a � ! $ @ � K h ] � � � ' � 3 � e # � S � ^ � [ � | E h � � � " �! �! �! �! �! � �! N �" : �" A $# ; f# J �# E �# A 3$ G u$ A �$ K �$ ; K% S �% M �% J )& E t& G �& F ' @ I' � �' -( ?( S( a( x( �( �( ! �( �( ) % +) ) Q) {) ' �) �) �) �) $ * 4* O* m* % �* $ �* �* �* " �* # + :+ S+ V+ Z+ k+ * �+ - �+ e �+ % E, B k, O �, �, % - * >- 5 i- �- + �- * �- + . <. " W. + z. + �. & �. �. / J 4/ R / �/ �/ � 0 " �0 1 & 01 % W1 }1 �1 7 �1 �1 6 �1 6 '2 $ ^2 �2 K �2 ? �2 P ,3 P }3 K �3 9 4 � T4 t �4 Y5 < c5 b �5 \ 6 ? `6 �6 . �6 + �6 7 E +7 q7 5 �7 & �7 �7 4 8 5 =8 * s8 �8 2 �8 6 �8 4 $9 < Y9 . �9 ~ �9 2 D: 6 w: 4 �: < �: . ; ~ O; i �; i 8< # �< E �< 8 = M E= & �= �= �= M �= [ ,> > �> t �> � <? 4 �@ �A @ C RD fE L lF �F : �F < G * LG + wG # �G �G �G ! �G H 2 'H > ZH D �H D �H #I � CI $ �I # �I J & AJ ( hJ ( �J * �J / �J , K BK ) bK �K �K ( �K * �K 1 L - QL ! L + �L > �L C M 8 PM E �M C �M 8 N E LN C �N C �N C O D ^O F �O B �O -P * <P ! gP " �P �P , �P �P �P F Q D YQ ? �Q �Q �Q R -R FR B IR G �R I �R { S C �S @ �S P T Q pT R �T O U V eU �U �U = �U 9 /V / iV �V ? �V ? �V H (W + qW �W ) �W ( �W V X 3 _X �X �X l �X Z !Z 8Z � BZ c �Z [ Y[ � �[ ! j\ 4 �\ - �\ �^ D _ M L_ � �_ � h` M 4a � �b � ]c d 4d Dd Wd Yd � ad K �d ? Ie 9 �e 6 �e H �e G Cf I �f B �f 9 g H Rg 6 �g E �g T h H mh G �h B �h Q Ai < �i � �i oj j �j �j �j �j �j k $k :k & Pk * wk �k & �k �k l l /l El `l {l �l �l �l �l �l m 3m Jm Mm Qm ! am �m , �m f �m $ 5n : Zn � �n o ! 5o 0 Wo 7 �o �o + �o * p ' 0p Xp ! np $ �p + �p # �p q "q > Bq F �q ' �q �q � r & �r ! �r * s $ 3s Xs gs ) �s �s * �s - �s $ t >t > ^t 7 �t U �t T +u > �u ) �u � �u j nv �v : �v e w b �w . �w x & +x ' Rx zx 9 �x �x 7 �x + y Fy 8 ey 1 �y ) �y �y " z ' <z # dz , �z �z z �z % M{ * s{ & �{ / �{ �{ w | g �| g �| ]} = x} 2 �} ? �} * )~ T~ r~ D �~ Z �~ 1 ! P S O � � � � � � � � � Є ? �� х 5 � ; � & Y� " �� �� Ć � � � * ,� 2 W� 4 �� 7 �� �� � � �� �� ؈ � � & !� % H� 4 n� $ �� ȉ ' � � &� " D� , g� $ �� $ �� ފ & �� : &� = a� 5 �� : Ջ : � 5 K� : �� : �� : �� : 2� ; m� ? �� > � (� , :� g� �� �� �� ͎ � > �� < 4� 3 q� �� �� ڏ �� � < � 4 O� 4 �� h �� 0 "� @ S� B �� ; ב < � 6 P� < �� Ē � F �� 7 @� ) x� �� 4 �� 4 � : � + U� �� �� �� N ݔ . ,� [� p� I � � � � � | W � � 0 $ � � � P � j J p � � � � � � H k � ( a < 4 � � " _ � � c b E � � � 9 � � � ? 5 � � 2 � � Y N # � , � U � � s � { � ; � > T 3 f � l G � � m � � � � V � & K � � � @ R � � = � � � X � Q z � � � d � � � \ � � M � 6 g � 7 � � ^ � � � i � � � L � � w � � � � ! [ ` � u � � � � S � � / . � 1 � � t � e 8 C � � � � Z h ) � � � n � q � � � � � A � � � B � o � � ~ � � � � � : � � � ] � O D v * � � � � } � F x � - � + ' � r % y � *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 <pgsql-bugs@lists.postgresql.org>. 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 --clone clone instead of copying files to new cluster -?, --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 -s, --socketdir=DIR socket directory to use (default CWD) -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: 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_control All non-template0 databases must allow connections, i.e. their pg_database.datallowconn must be true Analyzing all rows in the new cluster Cannot continue without required control information, terminating Cannot upgrade to/from the same system catalog version when using tablespaces. Checking cluster versions Checking database connection settings Checking database user is the install user Checking for contrib/isn with bigint-passing mismatch Checking for hash indexes Checking for incompatible "jsonb" data type Checking for incompatible "line" data type Checking for invalid "unknown" user columns Checking for large objects Checking for prepared transactions Checking for presence of required libraries Checking for reg* data types in user tables Checking for roles starting with "pg_" Checking for tables WITH OIDS Cloning user relation files 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 server Copying 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 objects Creating script to analyze new cluster Creating script to delete old cluster Database: %s Deleting files from new %s Failed to match up old and new tables in database "%s" Failure, exiting Finding the real data directory for the source cluster Finding the real data directory for the target cluster Freezing all rows in the new cluster Linking user relation files New cluster data and binary directories are from different major versions. New cluster database "%s" is not empty: found relation "%s.%s" 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 archives Restoring database schemas in the new cluster Restoring global objects in the new cluster Running in verbose mode Running this script will delete the old cluster's data files: %s SQL command failed %s %s Setting frozenxid and minmxid counters in new cluster Setting minmxid counter in new cluster Setting next OID for new cluster Setting next multixact ID and offset for new cluster Setting next transaction ID and epoch for new cluster Setting oldest multixact ID in new cluster Sync data directory to disk The 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 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 cloning "%s" to "%s" command too long connection to database failed: %s copying "%s" to "%s" could not add execute permission to file "%s": %s could not clone file between old and new data directories: %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 file "%s": %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": %s could 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 read permissions of directory "%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 cloning relation "%s.%s" ("%s" to "%s"): %s error while cloning relation "%s.%s": could not create file "%s": %s error while cloning relation "%s.%s": could not open file "%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 file cloning not supported on this platform 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 reside new cluster data resides ok old 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 reside old cluster data resides old 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 warning Project-Id-Version: pg_upgrade (PostgreSQL) 12 Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org PO-Revision-Date: 2019-06-03 18:40+0800 Last-Translator: Jie Zhang <zhangjie2@cn.fujitsu.com> Language-Team: Chinese (Simplified) <zhangjie2@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Language: zh_CN *群集是兼容的* *失败* 在运行pg_upgrade之前，您必须 : 创建一个新的数据库群集 (使用新版本的initdb) 关闭旧群集的postmaster服务 关闭新群集的postmaster服务 例如: pg_upgrade -d 旧集群/data -D 新集群/data -b 旧集群/bin -B 新集群/bin 或者 如果pg_upgrade在这一点之后失败，在继续之前必须重新初始化新集群. 如果要启动旧群集，则需要从%s/global/pg_control.old中 删除".old"后缀。 由于使用了"link"模式，一旦新群集启动， 旧群集就无法安全启动。 正在执行升级 ------------ 报告错误至 <pgsql-bugs@lists.postgresql.org>. 旧集群在"public"模式中定义了一个"plpython_call_handler"函数， 这是"pg_catalog"模式中定义的函数的副本。 您可以通过执行 在 psql中: \df *.plpython_call_handler 这个函数的"public"模式版本是由plpython的8.1之前的安装创建的, 必须删除才能完成pg_upgrade 因为它引用了一个现在已经过时的"plpython"共享对象文件。 通过运行以下命令，可以删除此函数的"public"模式版本: DROP FUNCTION public.plpython_call_handler() 在每个受影响的数据库中: 升级完成 -------- 警告：新数据目录不应位于旧数据目录中，例如 %s 警告：用户定义的表空间位置不应在数据目录中，例如 %s 运行pg_upgrade时，必须提供以下信息: 旧群集的数据目录 (-d DATADIR) 新群集的数据目录 (-D DATADIR) 旧版本的"bin"目录 (-b BINDIR) 新版本的"bin"目录 (-B BINDIR) 您的安装包含哈希索引。 这些索引在旧集群和新集群之间具有不同的内部格式，因此必须 使用REINDEX命令重新索引它们。 升级后，您将得到REINDEX指令。 您的安装包含哈希索引. These indexes have different 这些索引在旧集群和新集群之间具有不同的内部格式， 因此必须使用REINDEX命令重新索引它们。 文件 %s 当数据库超级用户通过psql执行时，将重新创建所有无效的索引； 在此之前，不会使用这些索引。 您的安装包含大对象。 新数据库有一个附加的大对象权限表， 因此必须为所有大对象定义默认权限。文件 %s 当数据库由psql执行时，超级用户将设置默认权限。 您的安装包含大对象。新数据库有一个附加的大对象权限表。 升级后，将向您提供一个命令，以使用默认权限填充 pg_largeobject_metadata表。 连接到数据库失败: %s 源数据库: 目标数据库: %s $ export PGDATAOLD=旧集群/data $ export PGDATANEW=新集群/data $ export PGBINOLD=旧集群/bin $ export PGBINNEW=新集群/bin $ pg_upgrade --clone 克隆而不是将文件复制到新群集 -?, --help 显示此帮助，然后退出 -B, --new-bindir=BINDIR 新群集可执行目录 -D, --new-datadir=DATADIR 新群集数据目录 -O, --new-options=OPTIONS 要传递到服务器的新群集选项 -P, --new-port=PORT 新群集端口号（默认值为%d） -U, --username=NAME 集群超级用户（默认值为"%s"） -V, --version 显示版本信息，然后退出 -b, --old-bindir=BINDIR 旧群集可执行目录 -c, --check 仅检查群集，不更改任何数据 -d, --old-datadir=DATADIR 旧群集数据目录 -j, --jobs 要同时使用的进程或线程数 -k, --link 使用硬链接来代替将文件拷贝到新群集 -o, --old-options=OPTIONS 要传递到服务器的旧群集选项 -p, --old-port=PORT 旧群集端口号（默认值为%d） -r, --retain 成功后保留SQL和日志文件 -s, --socketdir=DIR 要使用的套接字目录（默认值为CWD） -v, --verbose 启用详细的内部日志 C:\> set PGDATAOLD=旧集群/data C:\> set PGDATANEW=新集群/data C:\> set PGBINOLD=旧集群/bin C:\> set PGBINNEW=新集群/bin C:\> pg_upgrade WAL块大小 WAL段大小 块大小 下一个XID检查点 数据校验和版本 日期/时间是整数? 重置后的第一个WAL段 float8参数传递方法 大关系段大小 大对象块大小 最新检查点下一个MultiXactId 最新检查点下一个MultiXactOffset 最新检查点下一个OID 最新检查点最旧的MultiXactId 最大TOAST块大小 最大对齐方式 最大标识符长度 最大索引列数 pg_upgrade [选项]... 这是"%s.%s"上的索引 哪一个OID %u上的索引 哪一个是"%s.%s"的TOAST表 哪一个是OID %u的TOAST表 "%s"不是一个目录 %-*s %d: 控制数据检索问题 %d: 数据库集群状态问题 %d: pg_resetwal问题 %s %s %s.%s: %u到%u %s: 不能使用root用户运行 %s: 无法找到执行文件 向旧的global/pg_control添加".old"后缀 所有非template0数据库必须允许连接，即，它们的pg_database.dataallowconn必须为true 正在分析新群集中的所有行 没有所需的控制信息，无法继续，正在终止 使用表空间时无法升级到相同的系统目录版本。 或者，使用表空间时无法从同一系统目录版本升级。 正在检查群集版本 正在检查数据库连接设置 正在检查数据库用户是否为安装用户 正在检查contrib/isn和bigint-passing是否不匹配 正在检查哈希索引 正在检查不兼容的"jsonb"数据类型 正在检查不兼容的"line"数据类型 正在检查无效的"unknown"用户列 正在检查大对象 正在检查准备的交易记录 正在检查是否存在所需的库 正在检查用户表中的reg*数据类型 正在检查以"pg_"开头的角色 正在检查带有OIDS的表 正在克隆用户关系文件 有关故障的可能原因，请查阅"%s"的最后几行。 有关故障的可能原因，请查阅"%s"或 "%s"的最后几行。 正在将旧的 %s复制到新服务中 正在复制用户关系文件 无法创建删除旧群集数据文件的脚本. 因为用户定义的表空间或新集群的数据目录存在于旧集群目录中. 必须手动删除旧群集的内容. 正在创建数据库schemas的转储 正在创建全局对象的转储 正在创建用于分析新群集的脚本 正在创建删除旧群集的脚本 数据库: %s 正在从新%s中删除文件 未能匹配数据库"%s"中的新旧表 故障，退出 正在查找源群集的实际数据目录 正在查找目标群集的实际数据目录 正在冻结新群集中的所有行 正在链接用户关系文件 新的集群数据和二进制目录来自不同的主版本. 新群集数据库"%s"不是空的:找到关系"%s.%s" 在新群集中找不到与数据库"%2$s"中OID %1$u的旧关系的匹配项：%3$s 在旧群集中找不到与数据库"%2$s"中OID %1$u的新关系的匹配项: %3$s 旧的集群数据和二进制目录来自不同的主版本. 只能在新群集中定义安装用户. 优化器统计信息和可用空间信息不通过pg_upgrade进行传输，因此， 启动新服务器后，考虑运行: %s 优化器统计数据不会通过pg_upgrade传输,因此， 启动新服务器后，考虑运行: %s 选项: 正在执行一致性检查 ----------------------------- 在旧的活动的服务器上执行一致性检查 ------------------------------------------------ 数据库"%2$s"中OID %1$u的关系名称不匹配：旧名称 "%3$s.%4$s"，新名称"%5$s.%6$s" 从旧群集中删除问题函数以继续。 正在重置WAL归档 在新群集中还原数据库schemas 正在在新群集中还原全局对象 以详细模式运行 运行此脚本将删除旧群集的数据文件: %s SQL命令失败 %s %s 正在在新集群中设置frozenxid和minmxid计数器 正在在新群集中设置minmxid计数器 为新群集设置下一个OID 正在为新集群设置下一个多事务ID和偏移量 正在为新集群设置下一个事务ID和epoch 在新集群中设置最旧的多事务ID 将数据目录同步到磁盘 源群集包含准备好的事务 源集群包含以"pg_"开头的角色 源集群缺少集群状态信息: 源集群缺少一些必需的控制信息: 源群集未完全关闭。 在恢复模式下，源群集已关闭。要升级，请使用文档中的"rsync"，或将其作为主服务器关闭。 目标集群包含准备好的事务 目标集群包含以"pg_"开头的角色 目标集群缺少集群状态信息: 目标集群缺少一些必需的控制信息: 目标群集未完全关闭。 目标群集在恢复模式下关闭。要升级，请使用文档中的"rsync"，或将其作为主服务器关闭。 好像有一个postmaster正在为新群集服务。 请关闭那个postmaster，然后再试一次。 好像有一个postmaster正在为旧群集服务。 请关闭那个postmaster，然后再试一次。 执行"%s"时出现问题 此实用程序只能从PostgreSQL 8.4及更高版本升级. 此实用程序只能升级到PostgreSQL版本%s. 此实用程序不能用于降级到旧的主PostgreSQL版本. 请用 "%s --help" 获取更多的信息. 无法将%s重命名为%s。 使用方法: 检查活动服务器时，新端口号和旧端口号必须不同. 在检查pre-PG 9.1之前的活动旧服务器时，必须指定旧服务器的端口号. 您必须具有当前目录中的读写权限。 必须标识%s所在的目录。 请使用%s命令行选项或%s环境变量。 您的安装包含"contrib/isn"函数，这些函数依赖于bigint数据类型 旧群集和新群集传递的bigint值不同，因此当前无法升级此群集 您可以手动升级使用"contrib/isn"设施的数据库，并从旧集群中 删除"contrib/isn"，然后重新启动升级。 文件中有问题函数的列表: %s 您的安装包含用户表中的某个reg*数据类型. 这些数据类型引用了pg_upgrade不保留的系统OID, 因此当前无法升级此群集 . You can 您可以删除问题表并重新启动升级. 文件中有问题列的列表: %s 您的安装包含用户表中的"jsonb"数据类型. "jsonb"的内部格式在9.4测试版期间发生了更改，因此当前无法升级该集群。 您可以删除问题表并重新启动升级. 文件中有问题列的列表: %s 您的安装包含用户表中的"line"数据类型。 此数据类型更改了旧群集和新群集之间的内部格式和输入/输出格式， 因此当前无法升级此群集。 您可以删除问题表并重新启动升级。 文件中有问题列的列表: %s 您的安装包含用户表中的"unknown"数据类型。 表中不再允许此数据类型，因此当前无法升级此群集。 您可以删除问题表并重新启动升级。 文件中有问题列的列表 : %s 您的安装引用了新安装中缺少的可加载库。 您可以将这些库添加到新安装中，或者从旧安装中删除使用它们的函数。 文件中有问题库列表: %s 无法从Windows上的新群集数据目录内运行pg_upgrade 检查"%s"失败: %s 检查"%s"失败：无法执行（权限被拒绝） 检查"%s"失败：无法读取文件（权限被拒绝） 检查"%s"失败：不是常规文件 子进程异常退出：状态 %d 子工作线程异常退出: %s 正在将 "%s"克隆到"%s" 命令太长了 连接到数据库失败: %s 正在将 "%s"复制到"%s" 无法向文件"%s"添加执行权限: %s 无法在新旧数据目录之间克隆文件: %s 无法连接到用命令启动的源postmaster : %s 无法连接到用命令启动的目标postmaster : %s 无法创建文件 "%s": %s 无法在新旧数据目录之间创建硬链接: %s 在链接模式下，旧的和新的数据目录必须在同一文件系统上。 无法创建工作进程: %s 无法创建工作线程: %s 无法删除目录"%s" 无法确定当前目录 无法确定用户数 无法使用%s获取控制数据：%s 无法使用%s获取数据目录: %s 无法使用using %s获取pg_ctl的版本数据: %s 无法从%s获取pg_ctl版本输出 无法加载库 "%s": %s 无法打开文件"%s"用于读取: %s 无法打开文件 "%s": %s 无法打开版本文件: %s 无法从%s解析PG_VERSION文件 无法从文件"%2$s"读取第%1$d行: %3$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"时出错：无法写入文件 "%s": %s 复制关系"%s.%s"时出错：在文件"%s"中找到部分页 为关系"%s.%s"创建链接时出错（从"%s"到"%s"）: %s 正在执行: %s 无法获取"%s"的系统区域设置名称 无法获取当前区域设置 还原旧区域"%s"失败 致命的 此平台不支持文件克隆 新端口号无效 旧端口号无效 数据库"%s"的lc_collate不匹配: 旧的 "%s", 新的 "%s" 数据库"%s"的lc_ctype不匹配: 旧的 "%s", 新的 "%s" libpq环境变量%s具有非本地服务器值: %s 正在将"%s"链接到"%s" 映射为数据库"%s": 新群集二进制文件驻留 新群集数据驻留 OK 旧群集和新群集pg_controldata校验和版本不匹配 新旧pg_controldata WAL块大小无效或不匹配 新旧pg_controldata WAL段大小无效或不匹配 新旧pg_controldata对齐无效或不匹配 可能一个集群是32位安装，另一个是64位安装 新旧pg_controldata块大小无效或不匹配 新的和旧的pg_controldata日期/时间存储类型不匹配 旧的和新的pg_controldata大对象块大小无效或不匹配 新旧pg_controldata最大TOAST块大小无效或不匹配 新旧pg_controldata最大标识符长度无效或不匹配 新旧pg_controldata最大索引列无效或不匹配 新旧pg controldata最大关系段大小无效或不匹配 旧群集二进制文件驻留 旧群集数据驻留 旧群集不使用数据校验和，但新群集使用数据校验和 旧群集使用数据校验和，但新群集不使用 在新群集中找不到旧数据库"%s" 内存溢出 pg_ctl无法启动源服务器，或者连接失败 pg_ctl无法启动目标服务器，或连接失败 pg_upgrade将PostgreSQL集群升级到其他主版本。 relname: %s.%s: reloid: %u reltblspace: %s 正在将 "%s"重写为"%s" 表空间目录"%s"不存在 表空间路径"%s"不是目录 template0不能允许连接，即，其pg_database.datallowconn必须为false 用户提供的旧端口号%hu已更正为%hu waitpid()失败: %s 警告
💾 Save Changes
❌ Cancel