摘要:但如果涉及到跨大版本升級(jí)比如升級(jí)到,這種直接替換軟件就不行了,因?yàn)榭绨姹镜膬?nèi)部存儲(chǔ)形式發(fā)生了變化官方對(duì)于升級(jí)提供了種方法,這里遷移我使用了來(lái)進(jìn)行處理細(xì)節(jié)可以參考官方文檔。
1 場(chǎng)景描述
最近使用 postgresql 命令行比較多,就找了個(gè)類似 mycli 工具,pgcli,這個(gè)是針對(duì) postgresql 的,興沖沖的安裝了
brew install pgcli
沒(méi)想到這貨自動(dòng)幫我升級(jí)了 postgresql,我原來(lái)使用的是 9.5.7, 自動(dòng)幫我升級(jí)到了 9.6.3
查看升級(jí)日志 pg_upgrade_server.log
pg_ctl: another server might be running; trying to start server anyway waiting for server to start....FATAL: database files are incompatible with server DETAIL: The data directory was initialized by PostgreSQL version 9.5, which is not compatible with this version 9.6.3. stopped waiting pg_ctl: could not start server Examine the log output.
這是需要遷移數(shù)據(jù)的節(jié)奏啊,遷移之前需要的明白點(diǎn)什么
postgresql 中的升級(jí),如果針對(duì)小版本的升級(jí),比如 9.6.1 升級(jí)到 9.6.3(當(dāng)前的最新版本),只需要用 9.6.3 版本的軟件替換 9.6.1 版本的軟件即可,不需要做額外的操作,因?yàn)檎麄€(gè)大版本是相互兼容的,內(nèi)部存儲(chǔ)形式也是兼容的。但如果涉及到跨大版本升級(jí)比如 9.5.7 升級(jí)到 9.6.3,這種直接替換軟件就不行了,因?yàn)榭绨姹镜膬?nèi)部存儲(chǔ)形式發(fā)生了變化
官方對(duì)于升級(jí)提供了 3 種方法,這里遷移我使用了 pg_upgrade 來(lái)進(jìn)行處理, 細(xì)節(jié)可以參考官方文檔。
再進(jìn)行下一步之前,把 postgresql 服務(wù)關(guān)掉,執(zhí)行如下命令
brew services stop postgresql2 如何遷移數(shù)據(jù) 2.1 備份數(shù)據(jù)
mv /usr/local/var/postgresql /usr/local/var/postgresql.old2.2 使用新版本初始化新的數(shù)據(jù)庫(kù)
initdb /usr/local/var/postgres -E utf8 --locale=zh_CN.UTF-8
運(yùn)行結(jié)果
The files belonging to this database system will be owned by user "allen". This user must also own the server process. The database cluster will be initialized with locale "zh_CN.UTF-8". initdb: could not find suitable text search configuration for locale "zh_CN.UTF-8" The default text search configuration will be set to "simple". Data page checksums are disabled. creating directory /usr/local/var/postgres ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting dynamic shared memory implementation ... posix creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok syncing data to disk ... ok WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. Success. You can now start the database server using: pg_ctl -D /usr/local/var/postgres -l logfile start2.3 遷移舊數(shù)據(jù)
pg_upgrade 語(yǔ)法簡(jiǎn)單如下:
pg_upgrade -b 舊版本的bin目錄 -B 新版本的bin目錄 -d 舊版本的數(shù)據(jù)目錄 -D 新版本的數(shù)據(jù)目錄 [其他選項(xiàng)...]
然后運(yùn)行遷移命令
pg_upgrade -b /usr/local/Cellar/[email protected]/9.5.7/bin -B /usr/local/bin -d /usr/local/var/postgres.old -D /usr/local/var/postgres
運(yùn)行結(jié)果
Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database user is the install user ok Checking database connection settings ok Checking for prepared transactions ok Checking for reg* system OID user data types ok Checking for contrib/isn with bigint-passing mismatch ok Checking for roles starting with "pg_" ok Creating dump of global objects ok Creating dump of database schemas ok Checking for presence of required libraries ok Checking database user is the install user 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 and epoch for new cluster ok Deleting files from new pg_multixact/offsets ok Copying old pg_multixact/offsets to new server ok Deleting files from new pg_multixact/members ok Copying old pg_multixact/members to new server ok Setting next multixact ID and offset for new cluster ok Resetting WAL archives ok Setting frozenxid and minmxid counters in new cluster ok Restoring global objects in the new cluster ok Restoring database schemas in the 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
最后提示生成兩個(gè)腳本,一個(gè)是 analyze_new_cluster.sh,需要在新版本中執(zhí)行,用來(lái)收集統(tǒng)計(jì)信息,另一個(gè)是 delete_old_cluster.sh,用來(lái)刪除舊版本集群數(shù)據(jù),當(dāng)然為了安全起見(jiàn)可以等系統(tǒng)運(yùn)行幾天沒(méi)問(wèn)題再來(lái)刪除。
運(yùn)行下 analyze_new_cluster.sh 腳本
./analyze_new_cluster.sh
運(yùn)行結(jié)果如下:
This script will generate minimal optimizer statistics rapidly so your system is usable, and then gather statistics twice more with increasing accuracy. When it is done, your system will have the default level of optimizer statistics. If you have used ALTER TABLE to modify the statistics target for any tables, you might want to remove them and restore them after running this script because they will delay fast statistics generation. If you would like default statistics as quickly as possible, cancel this script and run: "/usr/local/bin/vacuumdb" --all --analyze-only vacuumdb: processing database "activity_tool": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "allen": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "cw": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "djexample": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "finance": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "iop": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "learn": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "postgres": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "servicemall": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "store": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "template1": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "test_store": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "uio": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "vbdev": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "vbdevelop": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "xiuzan": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "xzdevelop": Generating minimal optimizer statistics (1 target) vacuumdb: processing database "activity_tool": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "allen": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "cw": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "djexample": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "finance": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "iop": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "learn": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "postgres": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "servicemall": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "store": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "template1": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "test_store": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "uio": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "vbdev": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "vbdevelop": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "xiuzan": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "xzdevelop": Generating medium optimizer statistics (10 targets) vacuumdb: processing database "activity_tool": Generating default (full) optimizer statistics vacuumdb: processing database "allen": Generating default (full) optimizer statistics vacuumdb: processing database "cw": Generating default (full) optimizer statistics vacuumdb: processing database "djexample": Generating default (full) optimizer statistics vacuumdb: processing database "finance": Generating default (full) optimizer statistics vacuumdb: processing database "iop": Generating default (full) optimizer statistics vacuumdb: processing database "learn": Generating default (full) optimizer statistics vacuumdb: processing database "postgres": Generating default (full) optimizer statistics vacuumdb: processing database "servicemall": Generating default (full) optimizer statistics vacuumdb: processing database "store": Generating default (full) optimizer statistics vacuumdb: processing database "template1": Generating default (full) optimizer statistics vacuumdb: processing database "test_store": Generating default (full) optimizer statistics vacuumdb: processing database "uio": Generating default (full) optimizer statistics vacuumdb: processing database "vbdev": Generating default (full) optimizer statistics vacuumdb: processing database "vbdevelop": Generating default (full) optimizer statistics vacuumdb: processing database "xiuzan": Generating default (full) optimizer statistics vacuumdb: processing database "xzdevelop": Generating default (full) optimizer statistics Done3 重啟玩耍
brew services start postgresql
查看下服務(wù)狀態(tài)
brew services list
運(yùn)行結(jié)果
Name Status User Plist postgresql started allen /Users/allen/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
接著就可以愉快的使用 pgcli 了。
參考借鑒文章和文檔
https://www.postgresql.org/do...
https://stackoverflow.com/que...
http://www.cnblogs.com/space-...
http://www.cnblogs.com/shineq...
http://www.linuxidc.com/Linux...
文章版權(quán)歸作者所有,未經(jīng)允許請(qǐng)勿轉(zhuǎn)載,若此文章存在違規(guī)行為,您可以聯(lián)系管理員刪除。
轉(zhuǎn)載請(qǐng)注明本文地址:http://systransis.cn/yun/38964.html
摘要:小版本更新不受影響,比如到升級(jí)不受影響。下面介紹兩種升級(jí)方案可供選擇,均是官方文檔提及的方案官方文檔參考。方案命令是直接對(duì)舊的數(shù)據(jù)庫(kù)目錄文件進(jìn)行升級(jí)的方案,直接將舊版本的數(shù)據(jù)文件格式升級(jí)為新版本使用的格式。 PostgreSQL在默認(rèn)情況下,是不能跨版本升級(jí)的(9.4, 9.5, 9.6等等這些版本跨版本升級(jí)。小版本更新不受影響,比如9.6.1到9.6.2升級(jí)不受影響)。甚至PG為了數(shù)...
摘要:的問(wèn)題當(dāng)出現(xiàn)不能的時(shí)候,我也嘗試過(guò)這種提示里面的命令,可是還是不能解決這個(gè)問(wèn)題。解決方法一般自己機(jī)器上面的都是測(cè)試數(shù)據(jù),所以可以直接刪除掉舊的數(shù)據(jù)庫(kù)文件。解決方法然后就可以該干嘛干嘛了。 有些出現(xiàn)的問(wèn)題其實(shí)是不懂正確的流程,都是在試錯(cuò),可是還是學(xué)到了很多東西,寫下了,希望對(duì)我和大家都有幫助。 Homebrew 的問(wèn)題 當(dāng)我去運(yùn)行brew update的時(shí)候出現(xiàn)錯(cuò)誤untracked...
摘要:作者譚峰張文升出版日期年月頁(yè)數(shù)頁(yè)定價(jià)元本書特色中國(guó)開(kāi)源軟件推進(jìn)聯(lián)盟分會(huì)特聘專家撰寫,國(guó)內(nèi)多位開(kāi)源數(shù)據(jù)庫(kù)專家鼎力推薦。張文升中國(guó)開(kāi)源軟件推進(jìn)聯(lián)盟分會(huì)核心成員之一。 很高興《PostgreSQL實(shí)戰(zhàn)》一書終于出版,本書大體上系統(tǒng)總結(jié)了筆者 PostgreSQL DBA 職業(yè)生涯的經(jīng)驗(yàn)總結(jié),本書的另一位作者張文升擁有豐富的PostgreSQL運(yùn)維經(jīng)驗(yàn),目前就職于探探科技任首席PostgreS...
摘要:所以就安裝了另外一個(gè)很喜歡的數(shù)據(jù)庫(kù)的已經(jīng)修復(fù)了,后面會(huì)補(bǔ)上的安裝添加自啟動(dòng)初始化數(shù)據(jù)庫(kù)啟動(dòng)數(shù)據(jù)庫(kù)服務(wù)安裝上面是一條命令安裝自啟動(dòng)配置略安裝 系統(tǒng)升級(jí) 阿里云的FreeBSD系統(tǒng)默認(rèn)安裝版本是10.1,這個(gè)版本已經(jīng)超出了官方的維護(hù)時(shí)間了,所以首先要進(jìn)行系統(tǒng)的版本升級(jí) 設(shè)置當(dāng)前系統(tǒng)版本為10.1-release,setenv UNAME_r 10.1-RELEASE 修改update...
摘要:所以就安裝了另外一個(gè)很喜歡的數(shù)據(jù)庫(kù)的已經(jīng)修復(fù)了,后面會(huì)補(bǔ)上的安裝添加自啟動(dòng)初始化數(shù)據(jù)庫(kù)啟動(dòng)數(shù)據(jù)庫(kù)服務(wù)安裝上面是一條命令安裝自啟動(dòng)配置略安裝 系統(tǒng)升級(jí) 阿里云的FreeBSD系統(tǒng)默認(rèn)安裝版本是10.1,這個(gè)版本已經(jīng)超出了官方的維護(hù)時(shí)間了,所以首先要進(jìn)行系統(tǒng)的版本升級(jí) 設(shè)置當(dāng)前系統(tǒng)版本為10.1-release,setenv UNAME_r 10.1-RELEASE 修改update...
閱讀 1482·2021-11-24 09:39
閱讀 3663·2021-09-29 09:47
閱讀 1598·2021-09-29 09:34
閱讀 3108·2021-09-10 10:51
閱讀 2574·2019-08-30 15:54
閱讀 3250·2019-08-30 15:54
閱讀 898·2019-08-30 11:07
閱讀 1039·2019-08-29 18:36