Sync IvorySQL commit "Replace the pg_dialect control parameter with a core allow list"

hs-liuxh · hs-liuxh · commit 5e29ae80aa4f · 2026-06-30T13:07:56.000+08:00
diff --git a/CN/modules/ROOT/pages/master/ecosystem_components/pg_profile.adoc b/CN/modules/ROOT/pages/master/ecosystem_components/pg_profile.adoc
@@ -9,7 +9,7 @@ pg_profile 是一个用于 PostgreSQL 数据库性能分析的扩展工具，主
 
 pg_profile 硬依赖 dblink 与 plpgsql（其自身完全由 SQL 和 PL/pgSQL 编写，无需任何外部库或软件）；此外，建议安装 pg_stat_statements 扩展，以便在报告中获取 SQL 语句级别的统计信息。pg_profile 的版本与 PostgreSQL 的版本强相关，当前最高支持到 PG 18，具体的版本支持情况请查看 pg_profile 官方 github 仓库的 README.
 
-IvorySQL 的 PG 模式和 Oracle 兼容模式都已经适配 pg_profile。需要注意的是，在 Oracle 兼容模式下，pg_profile 在编译前，需要手动修改扩展源码的 control.tpl 文件，增加一个配置项 `pg_dialect = true` ，否则无法正常安装。
+IvorySQL 的 PG 模式和 Oracle 兼容模式都已经适配 pg_profile。
 
 项目地址：<https://github.com/zubkov-andrei/pg_profile>
 
@@ -18,13 +18,6 @@ IvorySQL 的 PG 模式和 Oracle 兼容模式都已经适配 pg_profile。需要
 == 安装启用
 
 === 源码编译
-IvorySQL 的 Oracle 兼容模式下安装 pg_profile，需要先修改 pg_profile 的 control.tpl 文件，增加 `pg_dialect` 配置项：
-[literal]
-----
-# pg_profile/control.tpl
-pg_dialect = true
-----
-
 执行源码编译和安装：
 [literal]
 ----
@@ -34,15 +27,7 @@ make -C contrib/pg_stat_statements install
 make -C contrib/pg_profile install
 ----
 
-安装产物为 `pg_profile.control` 与 `pg_profile--4.11.sql`。IvorySQL 的 Oracle 兼容模式下，可检查生成的 `pg_profile.control` 文件已携带 `pg_dialect` 声明：
-[literal]
-----
-default_version = '4.11'
-requires = 'dblink,plpgsql'
-superuser = false
-
-pg_dialect = true
-----
+安装产物为 `pg_profile.control` 与 `pg_profile--4.11.sql`。
 
 === 修改配置
 pg_profile 依赖的 pg_stat_statements 必须通过 `shared_preload_libraries` 在服务启动时加载。
@@ -77,16 +62,6 @@ SELECT extname, extversion FROM pg_extension WHERE extname = 'pg_profile';
  pg_profile | 4.11
 ----
 
-在 Oracle 兼容模式下，可执行下面的查询语句确认 pg_profile 的扩展函数已被固定到 PG 语法解析器：
-[literal]
-----
-SELECT proname, proconfig FROM pg_proc
-WHERE proname = 'take_sample' AND proconfig IS NOT NULL LIMIT 1;
-   proname   |                          proconfig
--------------+-------------------------------------------------------------
- take_sample | {ivorysql.compatible_mode=pg,search_path=profile}
-----
-
 == 使用流程
 
 === 创建样本
@@ -127,19 +102,4 @@ SELECT profile.get_report(1, 2);
 \o
 ----
 
-以上函数在 Oracle 模式会话（Oracle 端口/1521）中调用方式与结果完全一致。
-
-== 注意事项
-
-=== 适配说明
-IvorySQL 在 PG 模式下可直接安装使用 pg_profile 扩展，但在 Oracle 兼容模式下需要在编译时为 pg_profile 的 control.tpl 文件增加 `pg_dialect` 配置项，以启用 PG 语法解析器，避免安装失败。
-
-=== 适配边界
-`pg_dialect` 适配机制保护的是扩展自身的代码；调用方会话中书写的 SQL 仍按会话方言解析。在 Oracle 模式会话中调用 pg_profile 时，语句里用户自己的表达式需符合 Oracle 模式语法，例如：
-[literal]
-----
--- Oracle 会话中：PG 风格 interval 字面量会在会话解析期报错
-SELECT profile.set_server_size_sampling('local', current_time - interval '10 minute', ...);  -- 错误
-
--- 应使用会话方言可接受的写法，或在 PG 模式会话中执行管理操作
-----
+以上函数在 Oracle 模式会话（Oracle 端口/1521）中调用方式与结果完全一致。
diff --git a/CN/modules/ROOT/pages/master/ecosystem_components/pg_repack.adoc b/CN/modules/ROOT/pages/master/ecosystem_components/pg_repack.adoc
@@ -7,7 +7,7 @@
 == 概述
 pg_repack 是 PostgreSQL 的一个扩展，用于在线重整表和索引、消除存储膨胀。它能达到与 `VACUUM FULL` 类似的效果，回收空间，但几乎不阻塞业务读写。
 
-IvorySQL 的 PG 模式和 Oracle 兼容模式都已经适配 pg_repack。需要注意的是，在 Oracle 兼容模式下，pg_repack 在编译前，需要手动修改扩展源码的 lib/pg_repack.control.in 文件，增加一个配置项 `pg_dialect = true` ，否则无法正常安装。
+IvorySQL 的 PG 模式和 Oracle 兼容模式都已经适配 pg_repack。
 
 项目地址：<https://github.com/reorg/pg_repack>
 
@@ -47,13 +47,6 @@ VACUUM FULL 因没有"重写期间的并发变更捕获机制"，重写整表时
 git clone --branch ver_1.5.3 https://github.com/reorg/pg_repack.git
 ----
 
-IvorySQL 的 Oracle 兼容模式下安装 pg_repack，需要先修改 pg_repack 的 lib/pg_repack.control.in 文件，增加一个配置项 `pg_dialect = true`：
-[literal]
-----
-# pg_repack/lib/pg_repack.control.in
-pg_dialect = true
-----
-
 执行编译和安装：
 [literal]
 ----
diff --git a/EN/modules/ROOT/pages/master/ecosystem_components/pg_profile.adoc b/EN/modules/ROOT/pages/master/ecosystem_components/pg_profile.adoc
@@ -9,7 +9,7 @@ pg_profile is an extension tool for PostgreSQL database performance analysis. It
 
 pg_profile hard-depends on two extensions: dblink and plpgsql (it is written entirely in SQL and PL/pgSQL and requires no external libraries or software). Additionally, it is recommended to install the pg_stat_statements extension to obtain SQL statement-level statistics in the reports. The version of pg_profile is strongly tied to the version of PostgreSQL, currently supporting up to PG 18. For the specific version support, please refer to the README in the official pg_profile github repository.
 
-Both the PG mode and Oracle compatibility mode of IvorySQL have been adapted for pg_profile. Note that in Oracle compatibility mode, before compiling pg_profile, you need to manually modify the control.tpl file in the extension source code to add a configuration item `pg_dialect = true`, otherwise the installation will fail.
+Both the PG mode and Oracle compatibility mode of IvorySQL have been adapted for pg_profile. 
 
 Project address: <https://github.com/zubkov-andrei/pg_profile>
 
@@ -18,12 +18,6 @@ License: PostgreSQL License
 == Installation and Enabling
 
 === Source Code Compilation
-To install pg_profile in IvorySQL's Oracle compatibility mode, you need to first modify the control.tpl file of pg_profile to add the `pg_dialect` configuration item:
-[literal]
-----
-# pg_profile/control.tpl
-pg_dialect = true
-----
 
 Perform source code compilation and installation:
 [literal]
@@ -34,15 +28,7 @@ make -C contrib/pg_stat_statements install
 make -C contrib/pg_profile install
 ----
 
-The installation artifacts are `pg_profile.control` and `pg_profile--4.11.sql`. In IvorySQL's Oracle compatibility mode, you can verify that the generated `pg_profile.control` file carries the `pg_dialect` declaration:
-[literal]
-----
-default_version = '4.11'
-requires = 'dblink,plpgsql'
-superuser = false
-
-pg_dialect = true
-----
+The installation artifacts are `pg_profile.control` and `pg_profile--4.11.sql`. 
 
 === Modify Configuration
 The pg_stat_statements that pg_profile depends on must be loaded at server startup via `shared_preload_libraries`.
@@ -77,16 +63,6 @@ SELECT extname, extversion FROM pg_extension WHERE extname = 'pg_profile';
  pg_profile | 4.11
 ----
 
-In Oracle compatibility mode, you can run the following query to confirm that the extension functions of pg_profile have been pinned to the PG syntax parser:
-[literal]
-----
-SELECT proname, proconfig FROM pg_proc
-WHERE proname = 'take_sample' AND proconfig IS NOT NULL LIMIT 1;
-   proname   |                          proconfig
--------------+-------------------------------------------------------------
- take_sample | {ivorysql.compatible_mode=pg,search_path=profile}
-----
-
 == Usage Workflow
 
 === Create Samples
@@ -127,19 +103,4 @@ SELECT profile.get_report(1, 2);
 \o
 ----
 
-The above functions are invoked and produce identical results in an Oracle mode session (Oracle port/1521).
-
-== Notes
-
-=== Adaptation Description
-IvorySQL can directly install and use the pg_profile extension in PG mode. However, in Oracle compatibility mode, you need to add the `pg_dialect` configuration item to the control.tpl file of pg_profile at compile time to enable the PG syntax parser and avoid installation failure.
-
-=== Adaptation Boundary
-The `pg_dialect` adaptation mechanism protects the extension's own code; the SQL written in the caller's session is still parsed according to the session dialect. When calling pg_profile in an Oracle mode session, the user's own expressions in the statements must conform to Oracle mode syntax, for example:
-[literal]
-----
--- In an Oracle session: PG-style interval literals will cause an error during session parsing
-SELECT profile.set_server_size_sampling('local', current_time - interval '10 minute', ...);  -- ERROR
-
--- Use a syntax acceptable to the session dialect, or perform management operations in a PG mode session
-----
+The above functions are invoked and produce identical results in an Oracle mode session (Oracle port/1521).
diff --git a/EN/modules/ROOT/pages/master/ecosystem_components/pg_repack.adoc b/EN/modules/ROOT/pages/master/ecosystem_components/pg_repack.adoc
@@ -7,7 +7,7 @@
 == Overview
 pg_repack is an extension for PostgreSQL used to rebuild tables and indexes online and eliminate storage bloat. It can achieve effects similar to `VACUUM FULL` (reclaiming space), while barely blocking business read/write operations.
 
-Both the PG mode and Oracle compatibility mode of IvorySQL have been adapted for pg_repack. Note that in Oracle compatibility mode, before compiling pg_repack, you need to manually modify the lib/pg_repack.control.in file in the extension source code to add a configuration item `pg_dialect = true`, otherwise the installation will fail.
+Both the PG mode and Oracle compatibility mode of IvorySQL have been adapted for pg_repack. 
 
 Github: <https://github.com/reorg/pg_repack>
 
@@ -47,13 +47,6 @@ Pull the pg_repack source code:
 git clone --branch ver_1.5.3 https://github.com/reorg/pg_repack.git
 ----
 
-To install pg_repack in IvorySQL's Oracle compatibility mode, you need to first modify the lib/pg_repack.control.in file of pg_repack to add the `pg_dialect` configuration item:
-[literal]
-----
-# pg_repack/lib/pg_repack.control.in
-pg_dialect = true
-----
-
 Perform compilation and installation:
 [literal]
 ----
