Skip to content

Commit e11c246

Browse files
authored
Merge pull request #227 from jiaoshuntian/5_p2ivy
Add guide for Upgrading from PostgreSQL to IvorySQL
2 parents 823ac9e + 6162006 commit e11c246

File tree

2 files changed

+211
-0
lines changed

2 files changed

+211
-0
lines changed

CN/modules/ROOT/pages/4.4.adoc

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -153,6 +153,111 @@ pg_upgrade https://www.postgresql.org/docs/current/pgupgrade.html[文档]概述
153153

154154
这种升级方法可以用内置的逻辑复制工具和外部的逻辑复制系统如pglogical,Slony,Londiste,和Bucardo。
155155

156+
== 使用 pg_upgrade 将 PostgreSQL 升级到 IvorySQL
157+
158+
`pg_upgrade` 支持将原生 PostgreSQL 集群升级到 IvorySQL。当源集群为原生 PostgreSQL ,而目标为 IvorySQL 集群时,必须使用 `-g`(`--using-ora-pg`)参数。
159+
160+
从 PostgreSQL 升级到 IvorySQL 属于“跨产品”迁移,建议在生产环境操作前完成完整的测试验证,并制定详细的回滚方案。
161+
162+
=== 参数说明
163+
164+
[cols="1,3"]
165+
|===
166+
| 参数 | 说明
167+
168+
| `-g` / `--using-ora-pg`
169+
| 表示源集群为 PostgreSQL ,而目标为 IvorySQL 集群。启用此选项后,`pg_upgrade` 在连接两端集群时统一使用 PostgreSQL 标准端口,从而正确处理升级。
170+
|===
171+
172+
=== 升级步骤
173+
174+
==== 第一步:初始化新 IvorySQL 集群
175+
176+
[source,bash]
177+
----
178+
# 使用 IvorySQL 的 initdb 初始化新集群
179+
/opt/ivorysql/bin/initdb -D /data/ivorysql/data
180+
----
181+
182+
==== 第二步:停止源 PostgreSQL 集群
183+
184+
[source,bash]
185+
----
186+
/usr/lib/postgresql/16/bin/pg_ctl -D /data/pg/data stop
187+
----
188+
189+
==== 第三步:运行升级检查(可选)
190+
191+
使用 `-c` 仅做兼容性检查,不修改任何数据:
192+
193+
[source,bash]
194+
----
195+
/opt/ivorysql/bin/pg_upgrade \
196+
-b /usr/lib/postgresql/16/bin \ # 源 PG 可执行文件目录
197+
-B /opt/ivorysql/bin \ # 目标 IvorySQL 可执行文件目录
198+
-d /data/pg/data \ # 源 PG 数据目录
199+
-D /data/ivorysql/data \ # 目标 IvorySQL 数据目录
200+
-g \ # 源为 PostgreSQL,目标为 IvorySQL
201+
-c # 仅检查,不升级
202+
----
203+
204+
==== 第四步:执行升级
205+
206+
[source,bash]
207+
----
208+
/opt/ivorysql/bin/pg_upgrade \
209+
-b /usr/lib/postgresql/16/bin \
210+
-B /opt/ivorysql/bin \
211+
-d /data/pg/data \
212+
-D /data/ivorysql/data \
213+
-g
214+
----
215+
216+
==== 第五步:启动 IvorySQL 并验证
217+
218+
[source,bash]
219+
----
220+
/opt/ivorysql/bin/pg_ctl -D /data/ivorysql/data start
221+
222+
# 验证数据库是否正常
223+
/opt/ivorysql/bin/psql -p 5432 -c "SELECT version();"
224+
----
225+
226+
==== 第六步:清理旧集群
227+
228+
升级完成后,`pg_upgrade` 会生成一个清理脚本:
229+
230+
[source,bash]
231+
----
232+
./delete_old_cluster.sh
233+
----
234+
235+
=== 常用参数速查
236+
237+
[cols="1,2,2"]
238+
|===
239+
| 参数 | 长选项 | 说明
240+
241+
| `-b` | `--old-bindir` | 源集群可执行文件目录
242+
| `-B` | `--new-bindir` | 目标集群可执行文件目录
243+
| `-d` | `--old-datadir` | 源集群数据目录
244+
| `-D` | `--new-datadir` | 目标集群数据目录
245+
| `-g` | `--using-ora-pg` | 源为 PostgreSQL 升级到 IvorySQL
246+
| `-p` | `--old-port` | 源集群端口
247+
| `-P` | `--new-port` | 目标集群 PG 端口
248+
| `-q` | `--old-oraport` | 源集群 Oracle 端口
249+
| `-Q` | `--new-oraport` | 目标集群 Oracle 端口
250+
| `-j` | `--jobs` | 并行进程数
251+
| `-k` | `--link` | 使用硬链接替代文件复制
252+
| `-c` | `--check` | 仅检查兼容性,不执行升级
253+
| `-v` | `--verbose` | 输出详细日志
254+
|===
255+
256+
=== 注意事项
257+
258+
* `-g` 参数仅在 **源为纯 PostgreSQL 集群**、目标为 **IvorySQL** 时使用。若源集群已是 IvorySQL,则无需此参数。
259+
* 升级期间源集群和目标集群均须处于停止状态。
260+
* 升级前务必对源集群做完整备份。
156261

157262
== 管理IvorySQL版本
158263

EN/modules/ROOT/pages/4.4.adoc

Lines changed: 106 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -143,6 +143,112 @@ We can also create a fallback server using logical replication of an updated ver
143143

144144
This upgrade method can be used with built-in logical replication tools and external logical replication systems such as pglogical, Slony, Londiste, and Bucardo.
145145

146+
== Use pg_upgrade to upgrade PostgreSQL to IvorySQL
147+
148+
`pg_upgrade` supports upgrading native PostgreSQL clusters to IvorySQL. When the source cluster is native PostgreSQL and the target is an IvorySQL cluster, the `-g`(`--using-ora-pg`)parameter must be used.
149+
150+
Upgrading from PostgreSQL to IvorySQL is considered a "cross-product" migration. It is recommended to complete comprehensive testing and validation before performing the operation in a production environment, and to develop a detailed rollback plan.
151+
152+
=== Parameter description
153+
154+
[cols="1,3"]
155+
|===
156+
| parameter | description
157+
158+
| `-g` / `--using-ora-pg`
159+
| Indicates that the source cluster is PostgreSQL and the target is an IvorySQL cluster. When this option is enabled, `pg_upgrade` uniformly uses the PostgreSQL standard port when connecting to both clusters, ensuring proper handling of the upgrade.
160+
|===
161+
162+
=== Upgrade steps
163+
164+
==== Step 1: Initialize the new IvorySQL cluster
165+
166+
[source,bash]
167+
----
168+
# Use IvorySQL's initdb to initialize the new cluster
169+
/opt/ivorysql/bin/initdb -D /data/ivorysql/data
170+
----
171+
172+
==== Step 2: Stop the source PostgreSQL cluster
173+
174+
[source,bash]
175+
----
176+
/usr/lib/postgresql/16/bin/pg_ctl -D /data/pg/data stop
177+
----
178+
179+
==== Step 3: Run the upgrade check (optional)
180+
181+
Use `-c` to perform compatibility checks only without modifying any data:
182+
183+
[source,bash]
184+
----
185+
/opt/ivorysql/bin/pg_upgrade \
186+
-b /usr/lib/postgresql/16/bin \ # Source PG executable directory
187+
-B /opt/ivorysql/bin \ # Target IvorySQL executable directory
188+
-d /data/pg/data \ # Source PG data directory
189+
-D /data/ivorysql/data \ # Target IvorySQL data directory
190+
-g \ # Source is PostgreSQL, target is IvorySQL
191+
-c # Check only, do not upgrade
192+
----
193+
194+
==== Step 4: Perform the upgrade
195+
196+
[source,bash]
197+
----
198+
/opt/ivorysql/bin/pg_upgrade \
199+
-b /usr/lib/postgresql/16/bin \
200+
-B /opt/ivorysql/bin \
201+
-d /data/pg/data \
202+
-D /data/ivorysql/data \
203+
-g
204+
----
205+
206+
==== Step 5: Start IvorySQL and verify
207+
208+
[source,bash]
209+
----
210+
/opt/ivorysql/bin/pg_ctl -D /data/ivorysql/data start
211+
212+
# Verify if the database is functioning properly
213+
/opt/ivorysql/bin/psql -p 5432 -c "SELECT version();"
214+
----
215+
216+
==== Step 6: Clean up the old cluster
217+
218+
After the upgrade is completed,`pg_upgrade` will generate a cleanup script:
219+
220+
[source,bash]
221+
----
222+
./delete_old_cluster.sh
223+
----
224+
225+
=== Quick reference for common parameters
226+
227+
[cols="1,2,2"]
228+
|===
229+
| Parameters | Long options | Description
230+
231+
| `-b` | `--old-bindir` | Source cluster executable directory
232+
| `-B` | `--new-bindir` | Target cluster executable directory
233+
| `-d` | `--old-datadir` | Source cluster data directory
234+
| `-D` | `--new-datadir` | Target cluster data directory
235+
| `-g` | `--using-ora-pg` | Upgrade from PostgreSQL to IvorySQL
236+
| `-p` | `--old-port` | Source cluster port
237+
| `-P` | `--new-port` | Target cluster PG port
238+
| `-q` | `--old-oraport` | Source cluster Oracle port
239+
| `-Q` | `--new-oraport` | Target cluster Oracle port
240+
| `-j` | `--jobs` | Number of parallel processes
241+
| `-k` | `--link` | Use hard links instead of file copying
242+
| `-c` | `--check` | Check compatibility only, do not perform the upgrade
243+
| `-v` | `--verbose` | Output detailed logs
244+
|===
245+
246+
=== Precautions
247+
248+
* The `-g` parameter is only used when the **source is a pure PostgreSQL cluster**、and the target is **IvorySQL** . If the source cluster is already IvorySQL, this parameter is not needed.
249+
* Both the source and target clusters must be in a stopped state during the upgrade.
250+
* Be sure to perform a complete backup of the source cluster before upgrading.
251+
146252
== Managing IvorySQL Versions
147253

148254
IvorySQL is based on PostgreSQL and is updated at the same frequency as PostgreSQL, with one major release per year and one minor release per quarter. IvorySQL {ivorysql-version} is based on PostgreSQL {pg-version}, and all versions of IvorySQL are backward compatible.The relevant version features can be viewed by looking at https://www.ivorysql.org/en/releases-page/[Official Website]。

0 commit comments

Comments
 (0)