chore: upgrade declared pg version to 13.14.0 (#15177)

e2e_test/batch/catalog/version.slt.part

@@ -1,4 +1,4 @@
 query T
-select substring(version() from 1 for 14);
+select substring(version() from 1 for 16);
 ----
-PostgreSQL 9.5
+PostgreSQL 13.14

e2e_test/batch/functions/setting.slt.part

@@ -1,12 +1,12 @@
 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;
+SELECT current_setting('server_version_num') AS version;
 ----
-905
+130014
 
 query T
 SELECT set_config('client_min_messages', 'warning', false);

src/common/src/lib.rs

@@ -92,9 +92,9 @@ 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;
+pub const SERVER_VERSION_NUM: i32 = 130014;
 /// 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`.
 pub const SERVER_ENCODING: &str = "UTF8";
 /// see <https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-STANDARD-CONFORMING-STRINGS>