弁財天

yum --releasever=20 distro-sync で Fedora19の2117のパッケージをFedora20にアップグレードしたときのログ。

CPUやSSDやネットがこれだけ速くなったので一瞬でPC全体を書き換えることができる時代になってしまった。それが良いことなのか悪いことなのか。

Postgresqlが 9.2.6-1から9.3.1-2にバージョンアップしたのでマイグレーション作業がちょっとある。
PostgreSQL Upgrade - Fedora 20

#  yum install postgresql-upgrade
読み込んだプラグイン:fastestmirror, langpacks, refresh-packagekit
Loading mirror speeds from cached hostfile
 * fedora: ftp.riken.jp
 * livna: rpm.livna.org
 * rpmfusion-free: mirror.hust.edu.cn
 * rpmfusion-free-updates: mirror.hust.edu.cn
 * rpmfusion-nonfree: mirrors.hustunique.com
 * rpmfusion-nonfree-updates: mirrors.hustunique.com
 * updates: ftp.riken.jp
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ postgresql-upgrade.x86_64 0:9.3.2-2.fc20 を インストール
--> 依存性解決を終了しました。

依存性を解決しました

===============================================================================================================================================================================
 Package                                          アーキテクチャー                     バージョン                                  リポジトリー                           容量
===============================================================================================================================================================================
インストール中:
 postgresql-upgrade                               x86_64                               9.3.2-2.fc20                                updates                               2.5 M

トランザクションの要約
===============================================================================================================================================================================
インストール  1 パッケージ

総ダウンロード容量: 2.5 M
インストール容量: 9.1 M
Is this ok [y/d/N]: y
Downloading packages:
postgresql-upgrade-9.3.2-2.fc20.x86_64.rpm                                                                                                              | 2.5 MB  00:00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  インストール中          : postgresql-upgrade-9.3.2-2.fc20.x86_64                                                                                                         1/1 
  検証中                  : postgresql-upgrade-9.3.2-2.fc20.x86_64                                                                                                         1/1 

インストール:
  postgresql-upgrade.x86_64 0:9.3.2-2.fc20                                                                                                                                     

完了しました!
# pg_upgrade -b /usr/lib64/pgsql/postgresql-9.2/bin/ -B /usr/bin/ -d data92/ -D data

pg_upgrade: cannot be run as root
Failure, exiting
# su - postgres
-bash-4.2$ pwd
/var/lib/pgsql
-bash-4.2$ ls
backups  data  data92  initdb.log
-bash-4.2$ which pg_upgrade
/bin/pg_upgrade
-bash-4.2$ pg_upgrade -b /usr/lib64/pgsql/postgresql-9.2/bin/ -B /usr/bin/ -d data92/ -D data
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok
Checking database user is a superuser                       ok
Checking for prepared transactions                          ok
Checking for reg* system OID user data types                ok
Checking for contrib/isn with bigint-passing mismatch       ok
Creating dump of global objects                             ok
Creating dump of database schemas
                                                            ok
Checking for presence of required libraries                 ok
Checking database user is a superuser                       ok
Checking for prepared transactions                          ok

If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.

Performing Upgrade
------------------
Analyzing all rows in the new cluster                       ok
Freezing all rows on the new cluster                        ok
Deleting files from new pg_clog                             ok
Copying old pg_clog to new server                           ok
Setting next transaction ID for new cluster                 ok
Setting oldest multixact ID on new cluster                  ok
Resetting WAL archives                                      ok
Setting frozenxid counters in new cluster                   ok
Restoring global objects in the new cluster                 ok
Adding support functions to new cluster                     ok
Restoring database schemas in the new cluster
                                                            ok
Removing support functions from new cluster                 ok
Copying user relation files
                                                            ok
Setting next OID for new cluster                            ok
Sync data directory to disk                                 ok
Creating script to analyze new cluster                      ok
Creating script to delete old cluster                       ok

Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
    analyze_new_cluster.sh

Running this script will delete the old cluster's data files:
    delete_old_cluster.sh
-bash-4.2$