利用pg_upgrade更新数据库(从8.4升级到9.5)

本文利用pg_upgrade实现将8.4.18版本升级到9.5.0版本,8.4.18版本为RedHat系统自带pg数据库版本。

环境:Red Hat Enterprise Linux Server release 6.5 (Santiago) X86-64

查看手册看到可以利用pg_upgrade实现从8.4到9.5版本直接升级:

pg_upgrade supports upgrades from 8.3.X and later to the current major release of PostgreSQL, including snapshot and alpha releases.

下载postgresql9.5.0版本:

1.解压:

tar jxvf postgresql-9.5.0.tar.bz2

2.编译:

./configure --prefix=/usr/local/pgsql9.5.0 --with-pgport=5434 --with-wal-blocksize=16   //这里在编译时带with-wal-blocksize=16配置参数导致后面升级出现错误,具体到后面解释。注意指定目录,方便后面管理

***编译过程可能碰到错误:

configure: error: readline library notfound
If you have readline already installed, see config.log for detailson the
failure. It is possible the compiler isnt lookingin the proper directory.
Use --without-readline to disable readlinesupport.

解决方法:

rpm -qa | grep readline
yum search readline

找到符合配置的版本按照:
yum -y install -y readline-deve

安装完毕readline,重新执行上面编译命令。

3.安装:

gmake world
gmake install -world   //此处要加world

4.初始化数据库:

4.1 创建data数据目录:(可另指定其他位置,此处将指定在pg安装目录)

cd /usr/local/pgsql9.5.0
mkdir data

4.2 修改data目录权限,将其赋给postgres:

[[email protected] pgsql9.5.0]# chown -R postgres:postgres /usr/local/pgsql9.5.0/data    
[[email protected] pgsql9.5.0]# chmod -R 700  /usr/local/pgsql9.5.0/data

4.3 初始化:

-bash-4.1$ /usr/local/pgsql9.5.0/bin/initdb -E UTF8 -D /usr/local/pgsql9.5.0/data  --locale=C -U postgres -W   //locale=C这里在升级时报错,后续具体解释
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "C".
The default text search configuration will be set to "english".

Data page checksums are disabled.
....
初始化过程中会要求设置一个新的密码:postgres
...
Success. You can now start the database server using:

/usr/local/pgsql9.5.0/bin/pg_ctl -D /usr/local/pgsql9.5.0/data -l logfile start

***********************
:/usr/local/pgsql9.5.0/bin/为安装目录,/usr/local/pgsql9.5.0/data为数据目录
:初始化需要在postgres用户下进行,不能再root下
[[email protected] pgsql9.5.0]# /usr/local/pgsql9.5.0/bin/initdb -E UTF8 -D /usr/local/pgsql9.5.0/data  --locale=C -U postgres -W
initdb: cannot be run as root
Please log in (using, e.g., "su") as the (unprivileged) user that will
own the server process.
************************

5.安装pg_upgrade插件:

cd contrib
gamke
gmake install

5.修改postgresql.conf pg_hba.conf文件:

因为升级需要多次连接新老集群数据库实例, 所以修改为使用本地trust认证.
host    all             all             127.0.0.1/32            trust

端口使用注意使用不同的监听端口.(使用编译时候的指定端口:5434)

6.停老库:(新库没有启动,故这里不停)
-bash-4.1$ pg_ctl stop -m fast -D /var/lib/pgsql/data
waiting for server to shut down.... done
server stopped

7.更新:

首先创建一个用户执行升级的目录,该目录权限给postgres用户(执行更新时,会产一些升级文件,创建upgrade目录存储该些文件)
 su - root
 cd /usr/local/pgsql9.5.0
 mkdir upgrade
 chown postgres:postgres upgrade
 su - postgres
 cd /usr/local/pgsql9.5.0/upgrade

7.1检验更新:

-bash-4.1$ /usr/local/pgsql9.5.0/bin/pg_upgrade -c  -b /usr/bin -B /usr/local/pgsql9.5.0/bin -d /var/lib/pgsql/data -D /usr/local/pgsql9.5.0/data -p 5432 -P 5434 -U postgres                             //-c表示检验,-b/-B 表示老/新库bin目录,-d/-D表示老/新库数据目录,具体命令参考手册

检验时碰见以下问题:

1).wal-blocksize 问题

该问题是由前后两个版本wal-blocksize不同,因为之前在安装新版本时指定了wal-blocksize的大小为16k,但老版本是默认安装的,默认大小为8k,该参数大小只能在安装时改变,故需要重新安装pg数据库来解决该问题。

2).lc_collate values for database "postgres" do not match:  old "en_US.UTF-8", new "C" Failure, exiting

删除data数据目录,重新做一次初始化
/usr/local/pgsql9.5.0/bin/initdb -E UTF8 -D /usr/local/pgsql9.5.0/data  --locale=en_US.UTF-8 -U postgres -W

解决以上问题以后重新检验更新:

-bash-4.1$ /usr/local/pgsql9.5.0/bin/pg_upgrade -c  -b /usr/bin -B /usr/local/pgsql9.5.0/bin -d /var/lib/pgsql/data -D /usr/local/pgsql9.5.0/data -p 5432 -P 5434 -U postgres

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 invalid "line" user columns                    ok
Checking for large objects                                  ok
Checking for presence of required libraries                 ok
Checking database user is the install user                  ok
Checking for prepared transactions                          ok

*Clusters are compatible*

以上说明可以执行更新。

7.2 执行更新

-bash-4.1$ /usr/local/pgsql9.5.0/bin/pg_upgrade -b /usr/bin -B /usr/local/pgsql9.5.0/bin -d /var/lib/pgsql/data -D /usr/local/pgsql9.5.0/data -p 5432 -P 5434

*****

pg_upgrade有两种升级方式,一个是缺省的通过拷贝数据文件到新的data目录下,一个是创建硬链接。拷贝的方式升级较慢,但是原库还可用;硬链接的方式升级较快,但是原库不可用。以上是缺省的方式,硬链接方式升级的命令只需要添加--link

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 invalid "line" user columns                    ok
Checking for large objects                                  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
Setting oldest multixact ID on 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
Setting minmxid counter in new cluster                      ok
Creating newly-required TOAST tables                        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
Checking for large objects                                  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

升级过程是拷贝原来目录的数据到新版本指定的目录中,最后提示生成两个脚本,一个是analyze_new_cluster.sh,需要在新版本中执行,用来收集统计信息,另一个是 delete_old_cluster.sh,用来删除旧版本集群数据,当然为了安全起见可以等系统运行几天没问题再来删除。

8.启动新数据库

-bash-4.1$ pg_ctl start -D /usr/local/pgsql9.5.0/data

报错:

server starting
-bash-4.1$ FATAL:  unrecognized configuration parameter "dynamic_shared_memory_type"

解决方法:

原因是因为版本不一致导致,可能是我的主机上面被我编译了两个版本导致的,之前8.4postgresql.conf文件中没有该参数,升级后9.5的配置文件中有该参数,故出现不一致,
通过绝对路径启动数据库:
[[email protected] ~]# su - postgres
-bash-4.1$  /usr/local/pgsql9.5.0/bin/pg_ctl start -D /usr/local/pgsql9.5.0/data
server starting
-bash-4.1$ LOG:  database system was shut down at 2016-03-08 10:55:18 CST
LOG:  MultiXact member wraparound protections are now enabled
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections

进入数据库,此时psql无法进入:

-bash-4.1$ psql
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

通过指定psql路径进入:

-bash-4.1$ /usr/local/pgsql9.5.0/bin/psql  --指定路径
psql (9.5.0)
Type "help" for help.

postgres=#

9.执行收集统计信息的脚本:
-bash-4.1$ /usr/local/pgsql9.5.0/upgrade/analyze_new_cluster.sh
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/pgsql9.5.0/bin/vacuumdb" --all --analyze-only

vacuumdb: processing database "gedbs": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "postgres": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "template1": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "gedbs": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "postgres": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "template1": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "gedbs": Generating default (full) optimizer statistics
vacuumdb: processing database "postgres": Generating default (full) optimizer statistics
vacuumdb: processing database "template1": Generating default (full) optimizer statistics

Done

10.修改bash_profile文件中的PGDATA, PGPORT等参数(对postgres用户有效,客户端用其他用户登陆可能无效,修改/etc/profile对所有用户有效),修改PATH搜索路径,
不然在执行psql是会报版本不一致警告:

WARNING: psql version 8.4, server version 9.5.

11.启动数据库,pgadmin连接

报错:configure FATAL:  password authentication failed for user "postgres"

解决方法:

修改postgres用户密码,ALTER USER postgres PASSWORD ‘newPassword‘;

参考:http://stackoverflow.com/questions/7695962/postgresql-password-authentication-failed-for-user-postgres

12.新数据库稳定后,删除老版本软件
[[email protected] upgrade]# cat delete_old_cluster.sh
#!/bin/sh

rm -rf ‘/var/lib/pgsql/data‘

$ ./delete_old_cluster.sh

参考:

http://www.postgresql.org/docs/current/static/pgupgrade.html

http://my.oschina.net/liuyuanyuangogo/blog/500229
http://xmarker.blog.163.com/blog/static/22648405720145203428811/
http://906179271.iteye.com/blog/2263218
http://francs3.blog.163.com/blog/static/40576727201519521050/
http://wangwei.info/upgrade-postgresql-centos/

时间: 2024-08-07 01:52:33

利用pg_upgrade更新数据库(从8.4升级到9.5)的相关文章

PostgreSQL 利用pg_upgrade升级版本

参考:http://www.postgresql.org/docs/current/static/pgupgrade.html 概述 从低版本升级到 新版本,有几种可选的方案.一是使用pg_dump/pg_restore,该方法比较耗时,也即是停机时间比较长,特别是大数据量下,但是 稳定且易于操作.二是和MySQL那样利用复制的方式,停机时间短,但操作相对复杂.第三种就是利用pg_upgrade,重建系统表,相对停机时间较短. pg_upgrade 1. 语法 pg_upgrade -b old

关于系统数据库和服务现场升级的一些看法

本人目前在一家相当于创业公司吧. 工作也快满一年了,马上着手准备第二次出差去升级我们的系统,但是突然想到一件事情,让我颇有感触,是关于系统现场升级的. 我们迭代开发的系统隔一段时间就会需要到用户的现场去为其进行系统升级,其中升级包括客户端,服务端,以及数据库. 目前我们的做法是什么? 升级服务的方法是,将带过去的新的服务完全替换掉旧的服务,然后人工修改所有服务的相关配置. 升级数据库的方法是,在自己的笔记本上面部署一套我们需要升级的版本的数据库,然后到现场之后利用TOAD的schema的对比功能

C#使用DataSet Datatable更新数据库的三种实现方法

本文以实例形式讲述了使用DataSet Datatable更新数据库的三种实现方法,包括CommandBuilder 方法.DataAdapter 更新数据源以及使用sql语句更新.分享给大家供大家参考之用.具体方法如下: 一.自动生成命令的条件 CommandBuilder 方法 a)动态指定 SelectCommand 属性 b)利用 CommandBuilder 对象自动生成 DataAdapter 的 DeleteCommand.InsertCommand 和 UpdateCommand

EF6 Code First 模式更新数据库架构

定义好实体类和上下文类 在 Package Manager Console 输入以下命令 1.Enable-Migrations 启用数据迁移功能,该命令通常会在项目根目录下生成 Migrations 文件夹,文件夹内通常会有两个文件 201408020650593_InitialCreate.cs -- 迁移前的数据结构,前半段为时间戳 Configuration.cs -- 相关配置,是否需要自动迁移等,默认为 false 2.Add-Migration 增加迁移点,输入该命令后会要求你输入

iOS 使用FMDB事务批量更新数据库

当谈到“事务”时,我想到了sqlite本身是支持事务操作的,FMDB作为sqlite的上层封装也对事务进行了支持,那么说了这么多给不了解“事务”这个词的同学解释一下吧:通常一次 sqlite3_exec 就是一次事务,假如你要对数据库中的Stutent表插入新数据,那么该事务的具体过程是:开始新事物->插入数据->提交事务,那么当我们要往该表内插入500条数据,如果按常规操作处理就要执行500次“开始新事物->插入数据->提交事务”的过程. 好吧,今天的重点来了,举个例子:假如北京

CentOS环境利用mariadb(mysql)数据库使用golang实现分布式系统的Leader选举

一.准备工作 1.下载安装vmware,步骤省略. 2.下载CentOS系统ios包:http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Everything-1611.iso 3.下载安装Xshell5,步骤省略. 4.下载安装git,步骤省略. 5.mariadb用于golang的api:https://github.com/go-sql-driver/mysql 6.vmware中依次点击"创建新的虚拟机&q

EntityFramework 更新数据库字段的三种方法

例: 实体类: public class TestDbContext : DbContext { public DbSet<Test> Tests { get; set; } public TestDbContext() : base() { } } public class Test { public long ID { get; set; } public string Name { get; set; } public string Email { get; set; } public

sqlite自动更新数据库

写一个类继承自  SQLiteOpenHelper 系统会自动添加构造方法. onCreate方法.onUpgrade方法 当数据库里面数据或者表结构有所改动时,咱们需要升级数据库 这个时候,版本加1.在update里面做相应修改. 需要注意的是,如果需要测试update,每次开始测试,version 值增大,如果和上次的相同,就不会促发update方法了 下面贴上代码 先是原来的表结构,对应的代码 import android.content.Context; import android.d

使用DataSet Datatable 更新数据库的三种方式

1:自动生成命令的条件 CommandBuilder 方法a)动态指定 SelectCommand 属性b)利用 CommandBuilder 对象自动生成 DataAdapter 的 DeleteCommand.InsertCommand 和 UpdateCommand.c)为了返回构造 INSERT.UPDATE 和 DELETE .SQL CommandBuilder 必须执行 SelectCommand.即:必须额外经历一次到数据源的行程,这可能会降低性能.这也是自动生成命令的缺点.d)