diff --git a/CN/modules/ROOT/pages/master/containerization/operator_deployment.adoc b/CN/modules/ROOT/pages/master/containerization/operator_deployment.adoc index f47a8945..538d7f65 100644 --- a/CN/modules/ROOT/pages/master/containerization/operator_deployment.adoc +++ b/CN/modules/ROOT/pages/master/containerization/operator_deployment.adoc @@ -110,7 +110,7 @@ spec: 还发生了什么?IVYO 从 `metadata.name` 读取值,为 Ivory 集群命名为 `hippo`。此外,IVYO 通过查看 `spec.image` 和 `spec.backups.pgbackrest.image` 的值,分别确定了 Ivory 和 pgBackRest 使用的容器镜像。`spec.postgresVersion` 的值也很重要,它帮助 IVYO 跟踪你使用的 Ivory 主版本。 -IVYO 通过清单中的 `spec.instances` 部分知道要创建多少个 Ivory 实例。虽然 `name` 是可选的,但我们选择将其命名为 `instance1`。我们也可以在集群初始化期间创建多个副本和实例,但稍后在我们讨论 https://github.com/IvonySQL/ivory-operator/blob/master/docs/content/tutorial/high-availability.md[如何扩展并创建高可用 Ivory 集群] 时会详细介绍。 +IVYO 通过清单中的 `spec.instances` 部分知道要创建多少个 Ivory 实例。虽然 `name` 是可选的,但我们选择将其命名为 `instance1`。我们也可以在集群初始化期间创建多个副本和实例,但稍后在我们讨论 https://github.com/IvorySQL/ivory-operator/blob/master/docs/content/tutorial/high-availability.md[如何扩展并创建高可用 Ivory 集群] 时会详细介绍。 `ivorycluster` 自定义资源中非常重要的一部分是 `dataVolumeClaimSpec` 部分。它描述了 Ivory 实例将使用的存储,建模自 https://kubernetes.io/docs/concepts/storage/persistent-volumes/[Persistent Volume Claim]。如果你没有提供 `spec.instances.dataVolumeClaimSpec.storageClassName`,则将使用 Kubernetes 环境中的默认存储类。 @@ -1632,7 +1632,7 @@ spec: ---- == 监控 -虽然拥有 https://github.com/IvorySQL/ivory-operator/blob/master/docs/content/tutorial/high-availability.md[高可用性] 和 https://github.com/Ivory-operator/blob/master/docs/content/tutorial/disaster-recovery.md[灾难恢复] 系统可以在您的 IvorySQL 集群出现问题时提供帮助,但监控可以帮助您预防问题的发生。此外,监控可以帮助您诊断和解决可能导致性能下降的问题,而不是停机。 +虽然拥有 https://github.com/IvorySQL/ivory-operator/blob/master/docs/content/tutorial/high-availability.md[高可用性] 和 https://github.com/IvorySQL/ivory-operator/blob/master/docs/content/tutorial/disaster-recovery.md[灾难恢复] 系统可以在您的 IvorySQL 集群出现问题时提供帮助,但监控可以帮助您预防问题的发生。此外,监控可以帮助您诊断和解决可能导致性能下降的问题,而不是停机。 让我们看看 IVYO 如何允许您在集群中启用监控。 diff --git a/CN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc b/CN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc index e929a549..9a1c9c91 100644 --- a/CN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc +++ b/CN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc @@ -9,7 +9,7 @@ IvorySQL适配认证如下CPU架构: |==== | 序号 | 架构名称 | 适配品牌 | 全平台介质包下载 | 1 | x86_64 | Intel、AMD、兆芯、海光 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.amd64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.x86_64.rpm[rpm] -| 2 | aarch64 | 飞腾、鲲鹏 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.arm64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.aarch64.rpm[rpm] -| 3 | mips64el| 龙芯3000,龙芯4000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.mips64el.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.mips64el.rpm[rpm] -| 4 | loongarch64 | 龙芯5000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251118.loongarch64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251118.loongarch64.rpm[rpm] +| 2 | aarch64 | 飞腾、鲲鹏 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.arm64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.aarch64.rpm[rpm] +| 3 | mips64el| 龙芯3000,龙芯4000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.mips64el.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.mips64el.rpm[rpm] +| 4 | loongarch64 | 龙芯5000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.loongarch64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.loongarch64.rpm[rpm] |==== diff --git a/CN/modules/ROOT/pages/master/installation_guide.adoc b/CN/modules/ROOT/pages/master/installation_guide.adoc index 6c8fc004..67da8767 100644 --- a/CN/modules/ROOT/pages/master/installation_guide.adoc +++ b/CN/modules/ROOT/pages/master/installation_guide.adoc @@ -140,12 +140,12 @@ $ sudo apt -y install pkg-config libreadline-dev libicu-dev libldap2-dev uuid-de ** 获取deb包 ``` -$ sudo wget https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-a50789d-20250304.amd64.deb +$ sudo wget https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.amd64.deb ``` ** 安装deb包 ``` -$ sudo dpkg -i IvorySQL-5.0-a50789d-20250304.amd64.deb +$ sudo dpkg -i IvorySQL-5.0-9d890e9-20251120.amd64.deb ``` 数据库将被安装在/usr/ivory-5/路径下。 diff --git a/CN/modules/ROOT/pages/master/operation_guide.adoc b/CN/modules/ROOT/pages/master/operation_guide.adoc index 211d5fda..a5d96246 100644 --- a/CN/modules/ROOT/pages/master/operation_guide.adoc +++ b/CN/modules/ROOT/pages/master/operation_guide.adoc @@ -258,7 +258,7 @@ pg_upgrade https://www.postgresql.org/docs/current/pgupgrade.html[文档]概述 == 管理IvorySQL版本 -IvorySQL基于PostgreSQL开发,版本更新频率与PostgreSQL版本更新频率保持一致,每年更新一个大版本,每季度更新一个小版本。IvorySQL目前发布的版本有1.0到5.0,分别基于PostgreSQL 14.0到18.0进行开发,最新版本为IvorySQL 5.0,基于PostgreSQL 18.0进行开发。IvorySQL 的所有版本全部都做到了向下兼容。相关版本特性可以查看 https://www.ivorysql.org/zh-CN/releases-page[官网]。 +IvorySQL基于PostgreSQL开发,版本更新频率与PostgreSQL版本更新频率保持一致,每年更新一个大版本,每季度更新一个小版本。IvorySQL目前发布的版本有1.0到5.0,分别基于PostgreSQL 14.0到18.0进行开发,最新版本为IvorySQL 5.0,基于PostgreSQL 18.0进行开发。IvorySQL 的所有版本全部都做到了向下兼容。相关版本特性可以查看 https://github.com/IvorySQL/IvorySQL/releases[官网]。 == 管理IvorySQL数据库访问 diff --git a/CN/modules/ROOT/pages/master/release_notes.adoc b/CN/modules/ROOT/pages/master/release_notes.adoc index 4ef31d6b..0850fc13 100644 --- a/CN/modules/ROOT/pages/master/release_notes.adoc +++ b/CN/modules/ROOT/pages/master/release_notes.adoc @@ -161,7 +161,7 @@ IvorySQL 的主要代码仓库: - IvorySQL 数据库源码:https://github.com/IvorySQL/IvorySQL - IvorySQL 官网:https://github.com/IvorySQL/Ivory-www -- IvorySQL 文档:https://github.com/IvorySQL/IvorySQL-docs +- IvorySQL 文档:https://github.com/IvorySQL/ivorysql_docs - IvorySQL Docker:https://github.com/IvorySQL/docker_library == 贡献者名单 diff --git a/CN/modules/ROOT/pages/master/welcome.adoc b/CN/modules/ROOT/pages/master/welcome.adoc index efc84431..cf637f56 100644 --- a/CN/modules/ROOT/pages/master/welcome.adoc +++ b/CN/modules/ROOT/pages/master/welcome.adoc @@ -7,7 +7,7 @@ 从 https://github.com/IvorySQL/IvorySQL[Github 下载源码]开始。 == 发布 -请前往 https://www.ivorysql.org/releases-page[IvorySQL 发布页面]。 +请前往 https://github.com/IvorySQL/IvorySQL/releases[IvorySQL 发布页面]。 == 关于 IvorySQL IvorySQL 项目是瀚高软件提出的一个开源项目,旨在将 Oracle 兼容性功能添加到流行的 PostgreSQL 数据库中。 diff --git a/EN/modules/ROOT/pages/master/containerization/operator_deployment.adoc b/EN/modules/ROOT/pages/master/containerization/operator_deployment.adoc index bcd1adf0..45bb2cc9 100644 --- a/EN/modules/ROOT/pages/master/containerization/operator_deployment.adoc +++ b/EN/modules/ROOT/pages/master/containerization/operator_deployment.adoc @@ -539,7 +539,7 @@ What if IVYO was down during the downtime event? Failover would still occur: the === Synchronous Replication -IvorySQL supports synchronous replication, which is a replication mode designed to limit the risk of transaction loss. Synchronous replication waits for a transaction to be written to at least one additional server before it considers the transaction to be committed. For more information on synchronous replication, please read about IVYO's https://github.com/CrunchyData/postgres-operator/blob/master/docs/content/architecture/high-availability.md#synchronous-replication-guarding-against-transactions-loss[high availability architecture] +IvorySQL supports synchronous replication, which is a replication mode designed to limit the risk of transaction loss. Synchronous replication waits for a transaction to be written to at least one additional server before it considers the transaction to be committed. For more information on synchronous replication, please read about IVYO's https://github.com/CrunchyData/postgres-operator-examples[high availability architecture] To add synchronous replication to your Ivory cluster, you can add the following to your spec: @@ -922,7 +922,7 @@ IVYO lets you adjust CPU and memory within the `resources` sections of the `ivor - `spec.backups.pgbackrest.sidecars.pgbackrestConfig.resources` section, which sets the resources for the `pgbackrest-config` sidecar container. - `spec.backups.pgbackrest.jobs.resources` section, which sets the resources for any pgBackRest backup job. - `spec.backups.pgbackrest.restore.resources` section, which sets the resources for manual pgBackRest restore jobs. -- `spec.dataSource.ivorycluster.resources` section, which sets the resources for pgBackRest restore jobs created during the https://github.com/IvorySQL/ivory-operator/blob/master/docs/content/tutorial/clone-cluster.md[cloning] process. +- `spec.dataSource.ivorycluster.resources` section, which sets the resources for pgBackRest restore jobs created during the https://github.com/IvorySQL/ivory-operator/blob/master/docs/content/tutorial/create-cluster.md[cloning] process. The layout of these `resources` sections should be familiar: they follow the same pattern as the standard Kubernetes structure for setting https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/[container resources]. Note that these settings also allow for the configuration of https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/[QoS classes]. @@ -2364,7 +2364,7 @@ kubectl apply -k kustomize/ivory IVYO will detect the change and add the Exporter sidecar to all Ivory Pods that exist in your cluster. IVYO will also do the work to allow the Exporter to connect to the database and gather -metrics that can be accessed using the https://github.com/CrunchyData/postgres-operator-examples/tree/main/kustomize/monitoring[IVYO Monitoring] stack. +metrics that can be accessed using the https://github.com/CrunchyData/postgres-operator-examples[IVYO Monitoring] stack. ==== Configuring TLS Encryption for the Exporter @@ -2398,7 +2398,7 @@ for more information on configuring TLS for https://prometheus.io/[Prometheus]. === Accessing the Metrics Once the IvorySQL Exporter has been enabled in your cluster, follow the steps outlined in -https://github.com/CrunchyData/postgres-operator-examples/tree/main/kustomize/monitoring[IVYO Monitoring] to install the monitoring stack. This will allow you to deploy a https://github.com/CrunchyData/pgmonitor[pgMonitor] +https://github.com/CrunchyData/postgres-operator-examples[IVYO Monitoring] to install the monitoring stack. This will allow you to deploy a https://github.com/CrunchyData/pgmonitor[pgMonitor] configuration of https://prometheus.io/[Prometheus], https://grafana.com/[Grafana], and https://prometheus.io/docs/alerting/latest/alertmanager/[Alertmanager] monitoring tools in Kubernetes. These tools will be set up by default to connect to the Exporter containers on your Ivory Pods. diff --git a/EN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc b/EN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc index 856c8a35..6edec827 100644 --- a/EN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc +++ b/EN/modules/ROOT/pages/master/cpu_os_adaptation/cpu_architecture_adaptation.adoc @@ -9,7 +9,7 @@ IvorySQL adapts the following CPU architectures: |==== | Index | Architecture Name | Adapt to brands | Multi-platform Media Packages | 1 | x86_64 | Intel, AMD, ZHAOXIN, HYGON | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.amd64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.x86_64.rpm[rpm] -| 2 | aarch64 | Phytium, Kunpeng | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.arm64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.aarch64.rpm[rpm] -| 3 | mips64el| Loongson3000,Loongson4000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.mips64el.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.mips64el.rpm[rpm] -| 4 | loongarch64 | Loongson5000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251118.loongarch64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251118.loongarch64.rpm[rpm] +| 2 | aarch64 | Phytium, Kunpeng | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.arm64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.aarch64.rpm[rpm] +| 3 | mips64el| Loongson3000,Loongson4000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.mips64el.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.mips64el.rpm[rpm] +| 4 | loongarch64 | Loongson5000 | https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.loongarch64.deb[deb], https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-873c2f8-20251125.loongarch64.rpm[rpm] |==== diff --git a/EN/modules/ROOT/pages/master/ecosystem_components/pg_partman.adoc b/EN/modules/ROOT/pages/master/ecosystem_components/pg_partman.adoc index 9270a145..f465bd0d 100644 --- a/EN/modules/ROOT/pages/master/ecosystem_components/pg_partman.adoc +++ b/EN/modules/ROOT/pages/master/ecosystem_components/pg_partman.adoc @@ -23,7 +23,7 @@ License: PostgreSQL License IvorySQL 5.0 is installed, and the pg_config command can be successfully executed from the command line. === Source Installation -Get the source code from https://github.com/pgpartman/pg_partman: +Get the source code from https://github.com/pgpartman/pg_partman[pg_partman source code]: [literal] ---- git clone https://github.com/pgpartman/pg_partman.git diff --git a/EN/modules/ROOT/pages/master/getting-started/daily_monitoring.adoc b/EN/modules/ROOT/pages/master/getting-started/daily_monitoring.adoc index 789859c1..39a12101 100644 --- a/EN/modules/ROOT/pages/master/getting-started/daily_monitoring.adoc +++ b/EN/modules/ROOT/pages/master/getting-started/daily_monitoring.adoc @@ -738,8 +738,8 @@ The `pg_stat_database` view will contain one row for each database in the cluste | `deadlocks` | `bigint` | Number of deadlocks detected in this database | `checksum_failures` | `bigint` | Number of data page checksum failures detected in this database (or on a shared object), or NULL if data checksums are not enabled. | `checksum_last_failure` | `timestamp with time zone` | Time at which the last data page checksum failure was detected in this database (or on a shared object), or NULL if data checksums are noenabled. -| `blk_read_time` | `double precision` | Time spent reading data file blocks by backends in this database, in milliseconds (if [track_io_timing](https://www.postgresql.org/docs/currenruntime-config-statistics.html#GUC-TRACK-IO-TIMING) is enabled, otherwise zero) -| `blk_write_time` | `double precision` | Time spent writing data file blocks by backends in this database, in milliseconds (if [track_io_timing](https://www.postgresql.org/docs/currenruntime-config-statistics.html#GUC-TRACK-IO-TIMING) is enabled, otherwise zero) +| `blk_read_time` | `double precision` | Time spent reading data file blocks by backends in this database, in milliseconds (if [track_io_timing](https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-TRACK-IO-TIMING) is enabled, otherwise zero) +| `blk_write_time` | `double precision` | Time spent writing data file blocks by backends in this database, in milliseconds (if [track_io_timing](https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-TRACK-IO-TIMING) is enabled, otherwise zero) | `session_time` | `double precision` | Time spent by database sessions in this database, in milliseconds (note that statistics are only updated when the state of a session changes, so if sessions havbeen idle for a long time, this idle time won't be included) | `active_time` | `double precision` | Time spent executing SQL statements in this database, in milliseconds (this corresponds to the states `active` and `fastpath function call` inpg_stat_activity](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW)) | `idle_in_transaction_time` | `double precision` | Time spent idling while in a transaction in this database, in milliseconds (this corresponds to the states `idle in transaction` and `idle itransaction (aborted)` in [pg_stat_activity](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW)) diff --git a/EN/modules/ROOT/pages/master/installation_guide.adoc b/EN/modules/ROOT/pages/master/installation_guide.adoc index e511ae66..cb38f635 100644 --- a/EN/modules/ROOT/pages/master/installation_guide.adoc +++ b/EN/modules/ROOT/pages/master/installation_guide.adoc @@ -141,12 +141,12 @@ $ sudo apt -y install pkg-config libreadline-dev libicu-dev libldap2-dev uuid-de ** Getting deb ``` -$ sudo wget https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-a50789d-20250304.amd64.deb +$ sudo wget https://github.com/IvorySQL/IvorySQL/releases/download/IvorySQL_5.0/IvorySQL-5.0-9d890e9-20251120.amd64.deb ``` ** Installing deb ``` -$ sudo dpkg -i IvorySQL-5.0-a50789d-20250304.amd64.deb +$ sudo dpkg -i IvorySQL-5.0-9d890e9-20251120.amd64.deb ``` IvorySQL will then be installed in the /usr/ivory-5/ directory. diff --git a/EN/modules/ROOT/pages/master/operation_guide.adoc b/EN/modules/ROOT/pages/master/operation_guide.adoc index b0c92fbc..a5fc4ef8 100644 --- a/EN/modules/ROOT/pages/master/operation_guide.adoc +++ b/EN/modules/ROOT/pages/master/operation_guide.adoc @@ -248,7 +248,7 @@ After the upgrade is completed,`pg_upgrade` will generate a cleanup script: == Managing IvorySQL Versions -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 5.0 is based on PostgreSQL 18.0, 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]。 +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 5.0 is based on PostgreSQL 18.0, and all versions of IvorySQL are backward compatible.The relevant version features can be viewed by looking at https://github.com/IvorySQL/IvorySQL/releases[Official Website]。 == Managing IvorySQL database access diff --git a/EN/modules/ROOT/pages/master/release_notes.adoc b/EN/modules/ROOT/pages/master/release_notes.adoc index 695b03fd..94be4276 100644 --- a/EN/modules/ROOT/pages/master/release_notes.adoc +++ b/EN/modules/ROOT/pages/master/release_notes.adoc @@ -161,7 +161,7 @@ IvorySQL's development is maintained across four main repositories: - IvorySQL database source code: https://github.com/IvorySQL/IvorySQL - IvorySQL official website: https://github.com/IvorySQL/Ivory-www -- IvorySQL documentation: https://github.com/IvorySQL/IvorySQL-docs +- IvorySQL documentation: https://github.com/IvorySQL/ivorysql_docs - IvorySQL Docker: https://github.com/IvorySQL/docker_library == Contributors diff --git a/EN/modules/ROOT/pages/master/welcome.adoc b/EN/modules/ROOT/pages/master/welcome.adoc index 1e5c9e96..6dd78f11 100644 --- a/EN/modules/ROOT/pages/master/welcome.adoc +++ b/EN/modules/ROOT/pages/master/welcome.adoc @@ -7,7 +7,7 @@ Get started by https://github.com/IvorySQL/IvorySQL[downloading the code from Github]. == Releases -Go to https://www.ivorysql.org/releases-page[IvorySQL Release Page]. +Go to https://github.com/IvorySQL/IvorySQL/releases[IvorySQL Release Page]. == About IvorySQL IvorySQL project is an open source project proposed by Highgo Software to add the Oracle compatibility features into the popular PostgreSQL database.