chore: upgrade declared pg version to 13.14.0

risingwavelabs · Feb 21, 2024 · a2bf769 · a2bf769
1 parent 4197ad5
commit a2bf769
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/e2e_test/batch/functions/setting.slt.part b/e2e_test/batch/functions/setting.slt.part
@@ -1,7 +1,7 @@
 query T
 SELECT current_setting('server_version');
 ----
-9.5.0
+13.14.0
 
 query I
 SELECT CAST(current_setting('server_version_num') AS INT) / 100 AS version;

diff --git a/src/common/src/lib.rs b/src/common/src/lib.rs
@@ -92,7 +92,7 @@ pub const UNKNOWN_GIT_SHA: &str = "unknown";
 
 // The single source of truth of the pg parameters, Used in ConfigMap and current_cluster_version.
 // The version of PostgreSQL that Risingwave claims to be.
-pub const PG_VERSION: &str = "9.5.0";
+pub const PG_VERSION: &str = "13.14.0";
 /// The version of PostgreSQL that Risingwave claims to be.
 pub const SERVER_VERSION_NUM: i32 = 90500;
 /// Shows the server-side character set encoding. At present, this parameter can be shown but not set, because the encoding is determined at database creation time. It is also the default value of `client_encoding`.