/var/lib/pgsql/13/* /data_pg/ #将原数据目录下所有内容移动到新 数据目录下 # vi /usr/lib/systemd/system/postgresql-13.service #pg-13版本，修改systemd服 务文件，指定数据目录 #修改这行：Environment=PGDATA=/var/lib/pgsql/13/data/ 改为新的路径，如 下： /var/lib/pgsql/* /data_pg/ #将原数据目录下所有内容移动到新数 据目录下 # vi /usr/lib/systemd/system/postgresql.service #pg-10版本，修改systemd服务 文件，指定数据目录 #修改这行：Environment=PGDATA=/var/lib/pgsql/data/ 改为新的路径，如下： E ---------------- PostgreSQL 13.13 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-18)... postgres=# select usename from pg_user; #查看系统用户 usename ---------- postgres

boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red Hat Linux system one might find that /etc/rc.d/init.d/postgresql stop works. Very old versions might installation is sufficient before proceeding. --with-krb-srvnam=NAME The name of the Kerberos service principal. postgres is the default. There’s probably no reason to change this. --with-openssl Build 8.0.0 Build farm emu, snapshot 2004-12-06 11:35:03 3.6 Red Hat Linux AMD64 8.0.0 Tom Lane (), 2004-12-07 RHEL 3AS Red Hat Linux IA64 8.0.0 Tom Lane (), 2004-12-07

boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red Hat Linux system one might find that /etc/rc.d/init.d/postgresql stop works. Very old versions might installation is sufficient before proceeding. --with-krb-srvnam=NAME The name of the Kerberos service principal. postgres is the default. There’s probably no reason to change this. --with-openssl Build 2004-12-06 11:35:03 3.6 Red Hat Linux AMD64 8.0.0 Tom Lane (), 2004-12-07 RHEL 3AS Red Hat Linux IA64 8.0.0 Tom Lane (), 2004-12-07 RHEL 3AS Red Hat Linux PowerPC 8.0

......................................................................426 28.13. The Connection Service File .....................................................................................427 28 boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red Hat Linux system one might find that /etc/rc.d/init.d/postgresql stop works. Very old versions might installation is sufficient before proceeding. --with-krb-srvnam=NAME The default name of the Kerberos service principal. postgres is the default. There’s usually no reason to change this. --with-openssl Build

boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red Hat Linux system one might find that /etc/rc.d/init.d/postgresql stop works. Very old versions might installation is sufficient before proceeding. --with-krb-srvnam=NAME The default name of the Kerberos service principal. postgres is the default. There’s usually no reason to change this. --with-openssl Build 2004-12-06 11:35:03 3.6 Red Hat Linux AMD64 8.1.0 Tom Lane (), 2005-10-23 RHEL 4 Red Hat Linux IA64 8.1.0 Tom Lane (), 2005-10-23 RHEL 4 Red Hat Linux PowerPC 8.1.0

......................................................................457 29.14. The Connection Service File .....................................................................................457 29 boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red Hat Linux system one might find that /etc/rc.d/init.d/postgresql stop works. 4. If you are installing installation is sufficient before proceeding. --with-krb-srvnam=NAME The default name of the Kerberos service principal. postgres is the default. There’s usually no reason to change this. --with-openssl Build

......................................................................457 29.14. The Connection Service File .....................................................................................457 29 boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red Hat Linux system one might find that /etc/rc.d/init.d/postgresql stop works. 4. If you are installing installation is sufficient before proceeding. --with-krb-srvnam=NAME The default name of the Kerberos service principal. postgres is the default. There’s usually no reason to change this. --with-openssl Build

..................................................................... 837 33.16. The Connection Service File .................................................................... 838 33.17. LDAP Lookup examining the function body. As an example, consider this situation: CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple'); CREATE TABLE my_colors jsonb_path_ops); Consider the example of a table that stores JSON documents retrieved from a third-party web service, with a documented schema definition. A typical document is: { "guid": "9c36adc1-7fb5-4d5b-83b4-90356a46061a"

..................................................................... 798 33.16. The Connection Service File ............................................................... 798 33.17. LDAP Lookup of Connection examining the function body. As an example, consider this situation: CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple'); CREATE TABLE my_colors jsonb_path_ops); Consider the example of a table that stores JSON documents retrieved from a third-party web service, with a documented schema definition. A typical document is: { "guid": "9c36adc1-7fb5-4d5b-83b4-90356a46061a"

..................................................................... 845 34.16. The Connection Service File ............................................................... 845 34.17. LDAP Lookup of Connection examining the function body. As an example, consider this situation: CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple'); CREATE TABLE my_colors jsonb_path_ops); Consider the example of a table that stores JSON documents retrieved from a third-party web service, with a documented schema definition. A typical document is: { "guid": "9c36adc1-7fb5-4d5b-83b4-90356a46061a"