This is an automated email from the ASF dual-hosted git repository.
djwang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudberry-site.git
commit 06b75c84105438d2f53f0c522e6087cc84b73a05
Author: Dianjin Wang <wangdian...@gmail.com>
AuthorDate: Tue Sep 23 15:29:57 2025 +0800
Fix broken links
---
.../operate-with-db-objects/insert-update-delete-rows.md | 4 ++--
.../operate-with-db-objects/work-with-view-dependencies.md | 2 +-
docs/operate-with-data/sql-queries/basic-query-syntax.md | 2 +-
docs/operate-with-data/transactional-concurrency-control.md | 4 ++--
docs/operate-with-data/work-with-transactions.md | 4 ++--
docs/security/manage-roles-and-privileges.md | 2 +-
docs/sys-catalogs/gp_toolkit.md | 2 +-
docs/tutorials/best-practices/resource-group-best-practices.md | 2 +-
src/pages/team/new-committers.md | 2 +-
versioned_docs/version-1.x/basic-query-syntax.md | 2 +-
versioned_docs/version-1.x/cbdb-op-deploy-guide.md | 4 ++--
versioned_docs/version-1.x/cbdb-op-prepare-to-deploy.md | 4 ++--
versioned_docs/version-1.x/cbdb-rockylinux8-ubuntu-compile.md | 2 +-
versioned_docs/version-1.x/cbdb-rockylinux9-compile.md | 2 +-
versioned_docs/version-1.x/deploy-cbdb-with-single-node.md | 2 +-
versioned_docs/version-1.x/insert-update-delete-rows.md | 4 ++--
versioned_docs/version-1.x/performance/use-dynamic-tables.md | 2 +-
versioned_docs/version-1.x/security/manage-roles-and-privileges.md | 2 +-
versioned_docs/version-1.x/sys-admin/backup-and-restore/index.md | 2 +-
.../backup-and-restore/perform-incremental-backup-and-restore.md | 2 +-
versioned_docs/version-1.x/sys-utilities/gpcheckperf.md | 2 +-
versioned_docs/version-1.x/sys-utilities/gpsync.md | 2 +-
versioned_docs/version-1.x/transactional-concurrency-control.md | 4 ++--
versioned_docs/version-1.x/work-with-transactions.md | 4 ++--
.../operate-with-db-objects/insert-update-delete-rows.md | 4 ++--
.../operate-with-db-objects/work-with-view-dependencies.md | 2 +-
.../version-2.x/operate-with-data/sql-queries/basic-query-syntax.md | 2 +-
.../operate-with-data/transactional-concurrency-control.md | 4 ++--
.../version-2.x/operate-with-data/work-with-transactions.md | 4 ++--
versioned_docs/version-2.x/security/manage-roles-and-privileges.md | 2 +-
versioned_docs/version-2.x/sys-catalogs/gp_toolkit.md | 2 +-
.../tutorials/best-practices/resource-group-best-practices.md | 2 +-
32 files changed, 43 insertions(+), 43 deletions(-)
diff --git
a/docs/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
b/docs/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
index 47978a060e..40ad998b6b 100644
---
a/docs/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
+++
b/docs/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
@@ -121,5 +121,5 @@ You need to use the `VACUUM`, `VACUUM FULL`, and `VACUUM
ANALYZE` commands to ma
## See also
-- [Work with Transactions](/docs/work-with-transactions.md)
-- [Transactional Concurrency
Control](/docs/transactional-concurrency-control.md)
+- [Work with Transactions](../work-with-transactions.md)
+- [Transactional Concurrency Control](../transactional-concurrency-control.md)
diff --git
a/docs/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
b/docs/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
index a56169ad80..bae089c0f3 100644
---
a/docs/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
+++
b/docs/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
@@ -35,7 +35,7 @@ The following example queries list view information on
dependencies on tables an
- [List view definitions](#list-view-definitions)
- [List nested views](#list-nested-views)
-The example output is based on the [Example Data](#example_data) at the end of
this topic.
+The example output is based on the [Example data](#example-data) at the end of
this topic.
Also, you can use the first example query [Find direct view dependencies on a
table](#find-direct-view-dependencies-on-a-table) to find dependencies on
user-defined functions (or procedures). The query uses the catalog table
`pg_class` that contains information about tables and views. For functions, you
can use the catalog table `pg_proc` to get information about functions.
diff --git a/docs/operate-with-data/sql-queries/basic-query-syntax.md
b/docs/operate-with-data/sql-queries/basic-query-syntax.md
index 015f6d27f4..c8861cd81d 100644
--- a/docs/operate-with-data/sql-queries/basic-query-syntax.md
+++ b/docs/operate-with-data/sql-queries/basic-query-syntax.md
@@ -63,4 +63,4 @@ The above is just a brief overview of the basic query syntax
in Apache Cloudberr
## See also
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
+- [Insert, Update, and Delete
Rows](../operate-with-db-objects/insert-update-delete-rows.md)
diff --git a/docs/operate-with-data/transactional-concurrency-control.md
b/docs/operate-with-data/transactional-concurrency-control.md
index ba494aac0a..e7632a56b8 100644
--- a/docs/operate-with-data/transactional-concurrency-control.md
+++ b/docs/operate-with-data/transactional-concurrency-control.md
@@ -158,5 +158,5 @@ The following table shows the concurrent `UPDATE` or
`DELETE` commands that are
## See also
-- [Work with Transactions](/docs/work-with-transactions.md)
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
\ No newline at end of file
+- [Work with Transactions](./work-with-transactions.md)
+- [Insert, Update, and Delete
Rows](./operate-with-db-objects/insert-update-delete-rows.md)
\ No newline at end of file
diff --git a/docs/operate-with-data/work-with-transactions.md
b/docs/operate-with-data/work-with-transactions.md
index 0fd3830947..3bd8f72677 100644
--- a/docs/operate-with-data/work-with-transactions.md
+++ b/docs/operate-with-data/work-with-transactions.md
@@ -57,5 +57,5 @@ The default transaction isolation level in Apache Cloudberry
is `READ COMMITTED`
## See also
-- [Transactional Concurrency
Control](/docs/transactional-concurrency-control.md)
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
+- [Transactional Concurrency Control](./transactional-concurrency-control.md)
+- [Insert, Update, and Delete
Rows](./operate-with-db-objects/insert-update-delete-rows.md)
diff --git a/docs/security/manage-roles-and-privileges.md
b/docs/security/manage-roles-and-privileges.md
index 1389f7fbca..f6d371ba99 100644
--- a/docs/security/manage-roles-and-privileges.md
+++ b/docs/security/manage-roles-and-privileges.md
@@ -47,7 +47,7 @@ A database role might have a number of attributes that define
what sort of tasks
|`CONNECTION LIMIT *connlimit*`|If role can log in, this specifies how many
concurrent connections the role can make. -1 (the default) means no limit.|
|`CREATEEXTTABLE` or `NOCREATEEXTTABLE`|Determines whether a role is allowed
to create external tables. `NOCREATEEXTTABLE` is the default. For a role with
the `CREATEEXTTABLE` attribute, the default external table `type` is `readable`
and the default `protocol` is `gpfdist`. Note that external tables that use the
`file` protocol can only be created by superusers.|
|`PASSWORD '*password*'`|Sets the role's password. If you do not plan to use
password authentication you can omit this option. If no password is specified,
the password will be set to null and password authentication will always fail
for that user. A null password can optionally be written explicitly as
`PASSWORD NULL`.|
-|`DENY deny_interval` or `DENY deny_point` | Restricts access during an
interval, specified by day or day and time. For more information see
[Time-based authentication](#time-based-authentication).|
+|`DENY deny_interval` or `DENY deny_point` | Restricts access during an
interval, specified by day or day and time. For more information see
[Time-based authentication](./configure-db-auth.md#restrict-access-by-time).|
You can set these attributes when you create the role, or later using the
`ALTER ROLE` command. For example:
diff --git a/docs/sys-catalogs/gp_toolkit.md b/docs/sys-catalogs/gp_toolkit.md
index a4498c6c77..bae4938b7c 100644
--- a/docs/sys-catalogs/gp_toolkit.md
+++ b/docs/sys-catalogs/gp_toolkit.md
@@ -857,7 +857,7 @@ Apache Cloudberry considers a relation data file that is
present in the catalog,
Apache Cloudberry provides the following views to help identify if missing or
orphaned files exist in the current database:
-- [`gp_move_orphaned_files()`](#gp_move_orphaned_files)
+- [`gp_move_orphaned_files()`](#move-orphaned-data-files)
- [`gp_check_orphaned_files`](#gp_check_orphaned_files)
- [`gp_check_missing_files`](#gp_check_missing_files)
diff --git a/docs/tutorials/best-practices/resource-group-best-practices.md
b/docs/tutorials/best-practices/resource-group-best-practices.md
index 5dbe9c1084..875f08324b 100644
--- a/docs/tutorials/best-practices/resource-group-best-practices.md
+++ b/docs/tutorials/best-practices/resource-group-best-practices.md
@@ -9,7 +9,7 @@ Managing Apache Cloudberry resources with resource groups.
Memory, CPU, and concurrent transaction management have a significant impact
on performance in a Apache Cloudberry cluster. Resource groups are a newer
resource management scheme that enforce memory, CPU, and concurrent transaction
limits in Apache Cloudberry.
- [Configure Memory for Apache
Cloudberry](#configure-memory-for-apache-cloudberry)
-- [Memory Considerations when using Resource
Groups](#memory-considerations-when-using-resource-groups)
+- [Consider memory when using resource
groups](#consider-memory-when-using-resource-groups)
- [Configure Resource Groups](#configure-resource-groups)
- [Low Memory Queries](#low-memory-queries)
- [Administrative Utilities and admin_group
Concurrency](#administrative-utilities-and-admin_group-concurrency)
diff --git a/src/pages/team/new-committers.md b/src/pages/team/new-committers.md
index d3df751e58..92354c0908 100644
--- a/src/pages/team/new-committers.md
+++ b/src/pages/team/new-committers.md
@@ -11,7 +11,7 @@ To go through the whole process of inviting a new committer,
you need to be a Cl
| Steps | Notes
| Templates
[...]
|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------
[...]
-| **Discussion** | If any PPMC member recognize someone has
met our [requirements](/team#committers) and can be the potential committer,
please start a discussion in the priv...@cloudberry.apache.org. It's
recommended to provide the reason why you want to propose the new candidate.
The discussion will last at least 7 days.
| [[DISCUSS]](#committer-dis [...]
+| **Discussion** | If any PPMC member recognize someone has
met our [requirements](/team/#committers) and can be the potential committer,
please start a discussion in the priv...@cloudberry.apache.org. It's
recommended to provide the reason why you want to propose the new candidate.
The discussion will last at least 7 days.
| [[DISCUSS]](#committer-di [...]
| **Vote** | If the proposed candidate seems to be
received positively by a majority of those responding, please start a new
thread to vote the candidate. Let the Vote thread run for one week.
|
[[VOTE]](#committer-vote-t [...]
| **Announcing results** | No matter whether the result is positive or
negative, please raise a new thread to summarize. If the result is negative,
dismiss the following steps.
| [[RESULT]
[VOTE]](#committ [...]
| **Sending the invitation** | If the result is positive (achieved at
least 3 +1 votes and no vetoes), then send a invitation to the new committer
candidate. We give candidates a chance to decline committership in private.
They can post a reply to the PMC mailing list. If the new committer candidate
accepts, go to next. Otherwise, express the gratitude of Cloudberry community
and stop here.
| [Invitation](#committer-in [...]
diff --git a/versioned_docs/version-1.x/basic-query-syntax.md
b/versioned_docs/version-1.x/basic-query-syntax.md
index 015f6d27f4..8d52380afd 100644
--- a/versioned_docs/version-1.x/basic-query-syntax.md
+++ b/versioned_docs/version-1.x/basic-query-syntax.md
@@ -63,4 +63,4 @@ The above is just a brief overview of the basic query syntax
in Apache Cloudberr
## See also
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
+- [Insert, Update, and Delete Rows](./insert-update-delete-rows.md)
diff --git a/versioned_docs/version-1.x/cbdb-op-deploy-guide.md
b/versioned_docs/version-1.x/cbdb-op-deploy-guide.md
index 5f12377008..9a372723ce 100644
--- a/versioned_docs/version-1.x/cbdb-op-deploy-guide.md
+++ b/versioned_docs/version-1.x/cbdb-op-deploy-guide.md
@@ -4,7 +4,7 @@ title: Deploy Manually Using RPM Package
# Deploy Apache Cloudberry Manually Using RPM Package
-This document introduces how to manually deploy Apache Cloudberry on
physical/virtual machines using RPM package. Before reading this document, it
is recommended to first read the [Software and Hardware Configuration
Requirements](/docs/cbdb-op-software-hardware.md) and [Prepare to Deploy Apache
Cloudberry](/docs/cbdb-op-prepare-to-deploy.md).
+This document introduces how to manually deploy Apache Cloudberry on
physical/virtual machines using RPM package. Before reading this document, it
is recommended to first read the [Software and Hardware Configuration
Requirements](./cbdb-op-software-hardware.md) and [Prepare to Deploy Apache
Cloudberry](./cbdb-op-prepare-to-deploy.md).
The deployment method in this document is for production environments.
@@ -18,7 +18,7 @@ The example in this document uses CentOS 7.6 and deploys
Apache Cloudberry v1.0.
## Step 1: Prepare server nodes
-Read the [Prepare to Deploy Apache
Cloudberry](/docs/cbdb-op-prepare-to-deploy.md) document to prepare the server
nodes.
+Read the [Prepare to Deploy Apache Cloudberry](./cbdb-op-prepare-to-deploy.md)
document to prepare the server nodes.
## Step 2. Install the RPM package
diff --git a/versioned_docs/version-1.x/cbdb-op-prepare-to-deploy.md
b/versioned_docs/version-1.x/cbdb-op-prepare-to-deploy.md
index 58fa2dc9c3..64dc5a67ac 100644
--- a/versioned_docs/version-1.x/cbdb-op-prepare-to-deploy.md
+++ b/versioned_docs/version-1.x/cbdb-op-prepare-to-deploy.md
@@ -4,11 +4,11 @@ title: Prepare to Deploy
# Prepare to Deploy on Physical or Virtual Machine
-Before deploying Apache Cloudberry on physical or virtual machines, you need
to do some preparations. Read this document and [Software and Hardware
Configuration Requirements](/docs/cbdb-op-software-hardware.md) before you
start to deploy Apache Cloudberry.
+Before deploying Apache Cloudberry on physical or virtual machines, you need
to do some preparations. Read this document and [Software and Hardware
Configuration Requirements](./cbdb-op-software-hardware.md) before you start to
deploy Apache Cloudberry.
## Plan the deployment architecture
-Plan your deployment architecture based on the [Apache Cloudberry
Architecture](/docs/cbdb-architecture.md) and [Software and Hardware
Configuration Requirements](/docs/cbdb-op-software-hardware.md), and determine
the number of servers needed. Ensure that all servers are within a single
security group and have mutual trust configured.
+Plan your deployment architecture based on the [Apache Cloudberry
Architecture](./cbdb-architecture.md) and [Software and Hardware Configuration
Requirements](./cbdb-op-software-hardware.md), and determine the number of
servers needed. Ensure that all servers are within a single security group and
have mutual trust configured.
The deployment plan for the example of this document includes 1 coordinator +
1 standby + 3 segments (primary + mirror), totaling 5 servers.
diff --git a/versioned_docs/version-1.x/cbdb-rockylinux8-ubuntu-compile.md
b/versioned_docs/version-1.x/cbdb-rockylinux8-ubuntu-compile.md
index 387fed9439..7887c2f8d4 100644
--- a/versioned_docs/version-1.x/cbdb-rockylinux8-ubuntu-compile.md
+++ b/versioned_docs/version-1.x/cbdb-rockylinux8-ubuntu-compile.md
@@ -13,7 +13,7 @@ The source of this document is from the GitHub repository
[`apache/cloudberry`](
This document shares how to compile and install Apache Cloudberry on Rocky
Linux 8, RHEL 8, and Ubuntu. Note that this document is for developers to try
out Apache Cloudberry in a single-node environments. **DO NOT use this document
for production environments**.
-To learn how to compile and install Apache Cloudberry on Rocky Linux 9, see
[Compile on Rocky Linux 9](/docs/cbdb-rockylinux9-compile.md).
+To learn how to compile and install Apache Cloudberry on Rocky Linux 9, see
[Compile on Rocky Linux 9](./cbdb-rockylinux9-compile.md).
Take the following steps to compile and install Apache Cloudberry:
diff --git a/versioned_docs/version-1.x/cbdb-rockylinux9-compile.md
b/versioned_docs/version-1.x/cbdb-rockylinux9-compile.md
index 63e02253f2..a2f1ec1b45 100644
--- a/versioned_docs/version-1.x/cbdb-rockylinux9-compile.md
+++ b/versioned_docs/version-1.x/cbdb-rockylinux9-compile.md
@@ -10,7 +10,7 @@ The source of this document is from [Building Apache
Cloudberry (Incubating): A
This document is intended for developers interested in exploring and
potentially contributing to Apache Cloudberry. The build environment described
here is optimized for development and testing purposes only.
-To learn how to compile and install Apache Cloudberry on Rocky Linux 8 and
Ubuntu, see [Compile on Rocky Linux 8 and
Ubuntu](/docs/cbdb-rockylinux8-ubuntu-compile.md).
+To learn how to compile and install Apache Cloudberry on Rocky Linux 8 and
Ubuntu, see [Compile on Rocky Linux 8 and
Ubuntu](./cbdb-rockylinux8-ubuntu-compile.md).
## 1. Target audience
diff --git a/versioned_docs/version-1.x/deploy-cbdb-with-single-node.md
b/versioned_docs/version-1.x/deploy-cbdb-with-single-node.md
index 15c405cd98..fff2639885 100644
--- a/versioned_docs/version-1.x/deploy-cbdb-with-single-node.md
+++ b/versioned_docs/version-1.x/deploy-cbdb-with-single-node.md
@@ -430,7 +430,7 @@ systemctl status chronyd
### Step 3. Deploy Apache Cloudberry with a single computing node
-Use the scripting tool [`gpdemo`](/docs/sys-utilities/gpdemo.md) to quickly
deploy Apache Cloudberry. `gpdemo` is included in the RPM package and will be
installed in the `GPHOME/bin` directory along with the configuration scripts
(gpinitsystem, gpstart, and gpstop). `gpdemo` supports quickly deploying Apache
Cloudberry with a single computing node.
+Use the scripting tool [`gpdemo`](./sys-utilities/gpdemo.md) to quickly deploy
Apache Cloudberry. `gpdemo` is included in the RPM package and will be
installed in the `GPHOME/bin` directory along with the configuration scripts
(gpinitsystem, gpstart, and gpstop). `gpdemo` supports quickly deploying Apache
Cloudberry with a single computing node.
In the above [setting mount options for the XFS file
system](#set-mount-options-for-the-xfs-file-system), the XFS file system's
data directory is mounted on `/data0`. The following commands deploy a
single-computing-node cluster in this data directory:
diff --git a/versioned_docs/version-1.x/insert-update-delete-rows.md
b/versioned_docs/version-1.x/insert-update-delete-rows.md
index 47978a060e..b475edf0fc 100644
--- a/versioned_docs/version-1.x/insert-update-delete-rows.md
+++ b/versioned_docs/version-1.x/insert-update-delete-rows.md
@@ -121,5 +121,5 @@ You need to use the `VACUUM`, `VACUUM FULL`, and `VACUUM
ANALYZE` commands to ma
## See also
-- [Work with Transactions](/docs/work-with-transactions.md)
-- [Transactional Concurrency
Control](/docs/transactional-concurrency-control.md)
+- [Work with Transactions](./work-with-transactions.md)
+- [Transactional Concurrency Control](./transactional-concurrency-control.md)
diff --git a/versioned_docs/version-1.x/performance/use-dynamic-tables.md
b/versioned_docs/version-1.x/performance/use-dynamic-tables.md
index 2b156d3fea..ea933c618e 100644
--- a/versioned_docs/version-1.x/performance/use-dynamic-tables.md
+++ b/versioned_docs/version-1.x/performance/use-dynamic-tables.md
@@ -18,7 +18,7 @@ Dynamic tables are suitable for these scenarios:
## Comparison with materialized views
-Dynamic tables and [Answer Query Using Materialized
Views](/docs/performance/use-auto-materialized-view-to-answer-queries.md) have
these differences:
+Dynamic tables and [Answer Query Using Materialized
Views](./use-auto-materialized-view-to-answer-queries.md) have these
differences:
| **Feature** | Dynamic table
| AQUMV
|
|----------------------------|---------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|
diff --git a/versioned_docs/version-1.x/security/manage-roles-and-privileges.md
b/versioned_docs/version-1.x/security/manage-roles-and-privileges.md
index 1389f7fbca..7895192f8f 100644
--- a/versioned_docs/version-1.x/security/manage-roles-and-privileges.md
+++ b/versioned_docs/version-1.x/security/manage-roles-and-privileges.md
@@ -47,7 +47,7 @@ A database role might have a number of attributes that define
what sort of tasks
|`CONNECTION LIMIT *connlimit*`|If role can log in, this specifies how many
concurrent connections the role can make. -1 (the default) means no limit.|
|`CREATEEXTTABLE` or `NOCREATEEXTTABLE`|Determines whether a role is allowed
to create external tables. `NOCREATEEXTTABLE` is the default. For a role with
the `CREATEEXTTABLE` attribute, the default external table `type` is `readable`
and the default `protocol` is `gpfdist`. Note that external tables that use the
`file` protocol can only be created by superusers.|
|`PASSWORD '*password*'`|Sets the role's password. If you do not plan to use
password authentication you can omit this option. If no password is specified,
the password will be set to null and password authentication will always fail
for that user. A null password can optionally be written explicitly as
`PASSWORD NULL`.|
-|`DENY deny_interval` or `DENY deny_point` | Restricts access during an
interval, specified by day or day and time. For more information see
[Time-based authentication](#time-based-authentication).|
+|`DENY deny_interval` or `DENY deny_point` | Restricts access during an
interval, specified by day or day and time. This feature allows you to restrict
role access based on time constraints.|
You can set these attributes when you create the role, or later using the
`ALTER ROLE` command. For example:
diff --git a/versioned_docs/version-1.x/sys-admin/backup-and-restore/index.md
b/versioned_docs/version-1.x/sys-admin/backup-and-restore/index.md
index f36dfd6e64..95c5b28b98 100644
--- a/versioned_docs/version-1.x/sys-admin/backup-and-restore/index.md
+++ b/versioned_docs/version-1.x/sys-admin/backup-and-restore/index.md
@@ -12,7 +12,7 @@ Apache Cloudberry provides `gpbackup` and `gprestore` for
parallel backup and re
Backup files created with `gpbackup` are designed to provide future
capabilities for restoring individual database objects along with their
dependencies, such as functions and required user-defined data types.
-For details about backup and restore using `gpbackup` and `gprestore`, see
[Perform Full Backup and
Restore](/docs/sys-admin/backup-and-restore/perform-full-backup-and-restore.md)
and [Perform Incremental Backup and
Restore](/docs/sys-admin/backup-and-restore/perform-incremental-backup-and-restore.md).
+For details about backup and restore using `gpbackup` and `gprestore`, see
[Perform Full Backup and Restore](./perform-full-backup-and-restore.md) and
[Perform Incremental Backup and
Restore](./perform-incremental-backup-and-restore.md).
## Non-parallel backup with `pg_dump`
diff --git
a/versioned_docs/version-1.x/sys-admin/backup-and-restore/perform-incremental-backup-and-restore.md
b/versioned_docs/version-1.x/sys-admin/backup-and-restore/perform-incremental-backup-and-restore.md
index 6b1cc02706..ada96c7a84 100644
---
a/versioned_docs/version-1.x/sys-admin/backup-and-restore/perform-incremental-backup-and-restore.md
+++
b/versioned_docs/version-1.x/sys-admin/backup-and-restore/perform-incremental-backup-and-restore.md
@@ -4,7 +4,7 @@ title: Perform Incremental Backup and Restore
# Perform Incremental Backup and Restore
-Before reading this document, you are expected to first read the [Perform Full
Backup and
Restore](/docs/sys-admin/backup-and-restore/perform-full-backup-and-restore.md)
document.
+Before reading this document, you are expected to first read the [Perform Full
Backup and Restore](./perform-full-backup-and-restore.md) document.
To back up and restore tables incrementally, use the `gpbackup` and
`gprestore` utilities. Incremental backups include all specified heap tables,
and append-optimized tables (including column-oriented ones) that have changed.
Even a single row change triggers a backup of the entire append-optimized
table. For partitioned append-optimized tables, only the modified leaf
partitions are backed up.
diff --git a/versioned_docs/version-1.x/sys-utilities/gpcheckperf.md
b/versioned_docs/version-1.x/sys-utilities/gpcheckperf.md
index 4be44d9c3f..1e5daaa41a 100644
--- a/versioned_docs/version-1.x/sys-utilities/gpcheckperf.md
+++ b/versioned_docs/version-1.x/sys-utilities/gpcheckperf.md
@@ -140,4 +140,4 @@ $ gpcheckperf -f hostfile_gpchecknet_ic2 -r N --netperf -d
/tmp
## See also
-[gpssh](/docs/sys-utilities/gpssh.md), [gpsync](/docs/sys-utilities/gpsync.md)
+[gpssh](./gpssh.md), [gpsync](./gpsync.md)
diff --git a/versioned_docs/version-1.x/sys-utilities/gpsync.md
b/versioned_docs/version-1.x/sys-utilities/gpsync.md
index 7852263561..dfe8988bf2 100644
--- a/versioned_docs/version-1.x/sys-utilities/gpsync.md
+++ b/versioned_docs/version-1.x/sys-utilities/gpsync.md
@@ -90,4 +90,4 @@ gpsync -h sdw1 -h sdw2 myfuncs.so =:/usr/local/cloudberry/lib
## See also
-[gpssh](/docs/sys-utilities/gpssh.md),
[gpssh-exkeys](/docs/sys-utilities/gpssh-exkeys.md)
+[gpssh](./gpssh.md), [gpssh-exkeys](./gpssh-exkeys.md)
diff --git a/versioned_docs/version-1.x/transactional-concurrency-control.md
b/versioned_docs/version-1.x/transactional-concurrency-control.md
index ba494aac0a..de77b2aab7 100644
--- a/versioned_docs/version-1.x/transactional-concurrency-control.md
+++ b/versioned_docs/version-1.x/transactional-concurrency-control.md
@@ -158,5 +158,5 @@ The following table shows the concurrent `UPDATE` or
`DELETE` commands that are
## See also
-- [Work with Transactions](/docs/work-with-transactions.md)
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
\ No newline at end of file
+- [Work with Transactions](./work-with-transactions.md)
+- [Insert, Update, and Delete Rows](./insert-update-delete-rows.md)
\ No newline at end of file
diff --git a/versioned_docs/version-1.x/work-with-transactions.md
b/versioned_docs/version-1.x/work-with-transactions.md
index 0fd3830947..b2669db22f 100644
--- a/versioned_docs/version-1.x/work-with-transactions.md
+++ b/versioned_docs/version-1.x/work-with-transactions.md
@@ -57,5 +57,5 @@ The default transaction isolation level in Apache Cloudberry
is `READ COMMITTED`
## See also
-- [Transactional Concurrency
Control](/docs/transactional-concurrency-control.md)
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
+- [Transactional Concurrency Control](./transactional-concurrency-control.md)
+- [Insert, Update, and Delete Rows](./insert-update-delete-rows.md)
diff --git
a/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
b/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
index 47978a060e..40ad998b6b 100644
---
a/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
+++
b/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/insert-update-delete-rows.md
@@ -121,5 +121,5 @@ You need to use the `VACUUM`, `VACUUM FULL`, and `VACUUM
ANALYZE` commands to ma
## See also
-- [Work with Transactions](/docs/work-with-transactions.md)
-- [Transactional Concurrency
Control](/docs/transactional-concurrency-control.md)
+- [Work with Transactions](../work-with-transactions.md)
+- [Transactional Concurrency Control](../transactional-concurrency-control.md)
diff --git
a/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
b/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
index a56169ad80..bae089c0f3 100644
---
a/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
+++
b/versioned_docs/version-2.x/operate-with-data/operate-with-db-objects/work-with-view-dependencies.md
@@ -35,7 +35,7 @@ The following example queries list view information on
dependencies on tables an
- [List view definitions](#list-view-definitions)
- [List nested views](#list-nested-views)
-The example output is based on the [Example Data](#example_data) at the end of
this topic.
+The example output is based on the [Example data](#example-data) at the end of
this topic.
Also, you can use the first example query [Find direct view dependencies on a
table](#find-direct-view-dependencies-on-a-table) to find dependencies on
user-defined functions (or procedures). The query uses the catalog table
`pg_class` that contains information about tables and views. For functions, you
can use the catalog table `pg_proc` to get information about functions.
diff --git
a/versioned_docs/version-2.x/operate-with-data/sql-queries/basic-query-syntax.md
b/versioned_docs/version-2.x/operate-with-data/sql-queries/basic-query-syntax.md
index 015f6d27f4..c8861cd81d 100644
---
a/versioned_docs/version-2.x/operate-with-data/sql-queries/basic-query-syntax.md
+++
b/versioned_docs/version-2.x/operate-with-data/sql-queries/basic-query-syntax.md
@@ -63,4 +63,4 @@ The above is just a brief overview of the basic query syntax
in Apache Cloudberr
## See also
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
+- [Insert, Update, and Delete
Rows](../operate-with-db-objects/insert-update-delete-rows.md)
diff --git
a/versioned_docs/version-2.x/operate-with-data/transactional-concurrency-control.md
b/versioned_docs/version-2.x/operate-with-data/transactional-concurrency-control.md
index ba494aac0a..e7632a56b8 100644
---
a/versioned_docs/version-2.x/operate-with-data/transactional-concurrency-control.md
+++
b/versioned_docs/version-2.x/operate-with-data/transactional-concurrency-control.md
@@ -158,5 +158,5 @@ The following table shows the concurrent `UPDATE` or
`DELETE` commands that are
## See also
-- [Work with Transactions](/docs/work-with-transactions.md)
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
\ No newline at end of file
+- [Work with Transactions](./work-with-transactions.md)
+- [Insert, Update, and Delete
Rows](./operate-with-db-objects/insert-update-delete-rows.md)
\ No newline at end of file
diff --git
a/versioned_docs/version-2.x/operate-with-data/work-with-transactions.md
b/versioned_docs/version-2.x/operate-with-data/work-with-transactions.md
index 0fd3830947..3bd8f72677 100644
--- a/versioned_docs/version-2.x/operate-with-data/work-with-transactions.md
+++ b/versioned_docs/version-2.x/operate-with-data/work-with-transactions.md
@@ -57,5 +57,5 @@ The default transaction isolation level in Apache Cloudberry
is `READ COMMITTED`
## See also
-- [Transactional Concurrency
Control](/docs/transactional-concurrency-control.md)
-- [Insert, Update, and Delete Rows](/docs/insert-update-delete-rows.md)
+- [Transactional Concurrency Control](./transactional-concurrency-control.md)
+- [Insert, Update, and Delete
Rows](./operate-with-db-objects/insert-update-delete-rows.md)
diff --git a/versioned_docs/version-2.x/security/manage-roles-and-privileges.md
b/versioned_docs/version-2.x/security/manage-roles-and-privileges.md
index 1389f7fbca..f6d371ba99 100644
--- a/versioned_docs/version-2.x/security/manage-roles-and-privileges.md
+++ b/versioned_docs/version-2.x/security/manage-roles-and-privileges.md
@@ -47,7 +47,7 @@ A database role might have a number of attributes that define
what sort of tasks
|`CONNECTION LIMIT *connlimit*`|If role can log in, this specifies how many
concurrent connections the role can make. -1 (the default) means no limit.|
|`CREATEEXTTABLE` or `NOCREATEEXTTABLE`|Determines whether a role is allowed
to create external tables. `NOCREATEEXTTABLE` is the default. For a role with
the `CREATEEXTTABLE` attribute, the default external table `type` is `readable`
and the default `protocol` is `gpfdist`. Note that external tables that use the
`file` protocol can only be created by superusers.|
|`PASSWORD '*password*'`|Sets the role's password. If you do not plan to use
password authentication you can omit this option. If no password is specified,
the password will be set to null and password authentication will always fail
for that user. A null password can optionally be written explicitly as
`PASSWORD NULL`.|
-|`DENY deny_interval` or `DENY deny_point` | Restricts access during an
interval, specified by day or day and time. For more information see
[Time-based authentication](#time-based-authentication).|
+|`DENY deny_interval` or `DENY deny_point` | Restricts access during an
interval, specified by day or day and time. For more information see
[Time-based authentication](./configure-db-auth.md#restrict-access-by-time).|
You can set these attributes when you create the role, or later using the
`ALTER ROLE` command. For example:
diff --git a/versioned_docs/version-2.x/sys-catalogs/gp_toolkit.md
b/versioned_docs/version-2.x/sys-catalogs/gp_toolkit.md
index a4498c6c77..bae4938b7c 100644
--- a/versioned_docs/version-2.x/sys-catalogs/gp_toolkit.md
+++ b/versioned_docs/version-2.x/sys-catalogs/gp_toolkit.md
@@ -857,7 +857,7 @@ Apache Cloudberry considers a relation data file that is
present in the catalog,
Apache Cloudberry provides the following views to help identify if missing or
orphaned files exist in the current database:
-- [`gp_move_orphaned_files()`](#gp_move_orphaned_files)
+- [`gp_move_orphaned_files()`](#move-orphaned-data-files)
- [`gp_check_orphaned_files`](#gp_check_orphaned_files)
- [`gp_check_missing_files`](#gp_check_missing_files)
diff --git
a/versioned_docs/version-2.x/tutorials/best-practices/resource-group-best-practices.md
b/versioned_docs/version-2.x/tutorials/best-practices/resource-group-best-practices.md
index 5dbe9c1084..875f08324b 100644
---
a/versioned_docs/version-2.x/tutorials/best-practices/resource-group-best-practices.md
+++
b/versioned_docs/version-2.x/tutorials/best-practices/resource-group-best-practices.md
@@ -9,7 +9,7 @@ Managing Apache Cloudberry resources with resource groups.
Memory, CPU, and concurrent transaction management have a significant impact
on performance in a Apache Cloudberry cluster. Resource groups are a newer
resource management scheme that enforce memory, CPU, and concurrent transaction
limits in Apache Cloudberry.
- [Configure Memory for Apache
Cloudberry](#configure-memory-for-apache-cloudberry)
-- [Memory Considerations when using Resource
Groups](#memory-considerations-when-using-resource-groups)
+- [Consider memory when using resource
groups](#consider-memory-when-using-resource-groups)
- [Configure Resource Groups](#configure-resource-groups)
- [Low Memory Queries](#low-memory-queries)
- [Administrative Utilities and admin_group
Concurrency](#administrative-utilities-and-admin_group-concurrency)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cloudberry.apache.org
For additional commands, e-mail: commits-h...@cloudberry.apache.org
