From cebecd386db68a6e1ced3dc8eb577aacd1eafa60 Mon Sep 17 00:00:00 2001 From: sheetal Date: Thu, 1 Jul 2021 14:27:04 +0530 Subject: [PATCH 1/3] DB-142 Create an audit parameter to exclude or include certain user groups in or from auditing feature documentation Former-commit-id: 89354d254784511d86434ce6d946561c49b4f45d --- .../epas_compat_tools_guide/02_edb_loader.mdx | 6 +- ...strumentation_tools_architecture_DRITA.mdx | 8 +- .../epas/12/epas_compat_tools_guide/index.mdx | 2 +- ...02_summary_of_configuration_parameters.mdx | 2 +- ...audit_logging_configuration_parameters.mdx | 3 + .../02_selecting_sql_statements_to_audit.mdx | 202 +++++++++++++++++- .../03_reference_command_line_options.mdx | 2 +- .../01_supported_database_server_versions.mdx | 2 +- .../02_installing_language_pack.mdx | 12 +- .../04_uninstalling_language_pack.mdx | 6 +- .../epas_compat_tools_guide/02_edb_loader.mdx | 9 +- ...strumentation_tools_architecture_DRITA.mdx | 6 +- .../epas/13/epas_compat_tools_guide/index.mdx | 2 +- ...02_summary_of_configuration_parameters.mdx | 2 +- ...audit_logging_configuration_parameters.mdx | 3 + .../02_selecting_sql_statements_to_audit.mdx | 202 +++++++++++++++++- .../03_reference_command_line_options.mdx | 2 +- .../01_supported_database_server_versions.mdx | 2 +- .../02_installing_language_pack.mdx | 20 +- .../03_using_the_procedural_languages.mdx | 2 +- .../04_uninstalling_language_pack.mdx | 6 +- 21 files changed, 454 insertions(+), 47 deletions(-) diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx index 0b05a510c7b..539a3052536 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx @@ -148,7 +148,7 @@ Where `ENV_VARIABLE` is the environment variable that is set to the directory pa The `EDBLDR_ENV_STYLE` environment variable instructs Advanced Server to interpret environment variable references as Windows-styled references or Linux-styled references irregardless of the operating system on which EDB\*Loader resides. You can use this environment variable to create portable control files for EDB\*Loader. - On a Windows system, set `EDBLDR_ENV_STYLE` to `linux` or `unix` to instruct Advanced Server to recognize Linux-style references within the control file. -- On a Linux system, set `EDBLDR_ENV_STYLE` to windows to instruct Advanced Server to recognize Windows-style references within the control file. +- On a Linux system, set `EDBLDR_ENV_STYLE` to `windows` to instruct Advanced Server to recognize Windows-style references within the control file. The operating system account `enterprisedb` must have read permission on the directory and file specified by `data_file`. @@ -514,7 +514,7 @@ The following is the corresponding delimiter-separated data file: 9104,"JONES, JR.",MANAGER,7839,02-APR-09,7975.00,20 ``` -The use of the `TRAILING NULLCOLS` clause allows the last field supplying the comm column to be omitted from the first and last records. The `comm` column is set to null for the rows inserted from these records. +The use of the `TRAILING NULLCOLS` clause allows the last field supplying the `comm` column to be omitted from the first and last records. The `comm` column is set to null for the rows inserted from these records. The double quotation mark enclosure character surrounds the value `JONES, JR.` in the last record since the comma delimiter character is part of the field value. @@ -747,7 +747,7 @@ SELECT * FROM emp WHERE empno > 9100; **NULLIF Clause** -The following example uses the `NULLIF` clause on the sal column to set it to null for employees of job `MANAGER` as well as on the comm column to set it to null if the employee is not a `SALESMAN` and is not in department `30`. In other words, a comm value is accepted if the employee is a `SALESMAN` or is a member of department `30`. +The following example uses the `NULLIF` clause on the `sal` column to set it to null for employees of job `MANAGER` as well as on the `comm` column to set it to null if the employee is not a `SALESMAN` and is not in department `30`. In other words, a `comm` value is accepted if the employee is a `SALESMAN` or is a member of department `30`. The following is the control file: diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx index c0c931a6abe..49630679e96 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx @@ -830,7 +830,7 @@ The information displayed in the `DATA from pg_statio_all_tables` section includ | `TIDX READ` | The number of toast index blocks read. | | `TIDX HIT` | The number of toast index blocks hit. | -```Text +```text DATA from pg_stat_all_indexes SCHEMA RELATION INDEX @@ -1059,7 +1059,7 @@ function_name(, , , ) `scope` - scope determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: + `scope` determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: - `SYS` indicates that the function should return information about system defined tables. A table is considered a system table if it is stored in one of the following schemas: `pg_catalog`, `information_schema`, or `sys`. - `USER` indicates that the function should return information about user-defined tables. @@ -1186,7 +1186,7 @@ statio_tables_rpt(, , , ) `scope` - scope determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: + `scope` determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: - `SYS` indicates that the function should return information about system defined tables. A table is considered a system table if it is stored in one of the following schemas: `pg_catalog`, `information_schema`, or `sys`. - `USER` indicates that the function should return information about user-defined tables. @@ -1273,7 +1273,7 @@ stat_indexes_rpt(, , , ) `scope` - scope determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: + `scope` determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: - `SYS` indicates that the function should return information about system defined tables. A table is considered a system table if it is stored in one of the following schemas: `pg_catalog, information_schema`, or `sys`. - `USER` indicates that the function should return information about user-defined tables. diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx index 06f493cd0e4..fa2fdd7cae5 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx @@ -28,7 +28,7 @@ The EDB\*Plus command line client provides a user interface to Advanced Server t - Execute OS commands - Record output -For detailed installation and usage information about EDB\*Plus, see the EDB\*Plus User's Guide, available from the EnterpriseDB website at: +For detailed installation and usage information about EDB\*Plus, see the *EDB\*Plus User's Guide*, available from the EnterpriseDB website at: [https://www.enterprisedb.com/docs/p/edbplus](/epas/latest/edb_plus/) diff --git a/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx b/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx index 915bd8080c6..4316544197d 100644 --- a/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx +++ b/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx @@ -229,7 +229,7 @@ The following table shows the summary of configuration parameters: | `log_temp_files` | Session | Immediate | Superuser | Log the use of temporary files larger than this number of kilobytes. | | | `log_timezone` | Cluster | Reload | EPAS service account | Sets the time zone to use in log messages. | | | `log_truncate_on_rotation` | Cluster | Reload | EPAS service account | Truncate existing log files of same name during log rotation. | | -| `logging_collector` | Cluster | Restart | EPAS service account | Start a subprocess to capture stderr output and/or csvlogs into log files. | | +| `logging_collector` | Cluster | Restart | EPAS service account | Start a subprocess to capture stderr output and/or csv logs into log files. | | | `maintenance_work_mem` | Session | Immediate | User | Sets the maximum memory to be used for maintenance operations. | | | `max_connections` | Cluster | Restart | EPAS service account | Sets the maximum number of concurrent connections. | | | `max_files_per_process` | Cluster | Restart | EPAS service account | Sets the maximum number of simultaneously open files for each server process. | | diff --git a/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx b/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx index 98151a32d99..99e20cd5478 100644 --- a/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx +++ b/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx @@ -60,4 +60,7 @@ Use the following configuration parameters to control database auditing. See [Su Set to `syslog` to use the syslog process and its location as configured in the `/etc/syslog.conf` file. The `syslog` setting is valid for Advanced Server running on a Linux host and is not supported on Windows systems. **Note:** In recent Linux versions, syslog has been replaced by `rsyslog` and the configuration file is in `/etc/rsyslog.conf`. +!!! Note + Advanced Server allows administrative users associated with administrative privileges to audit statements by any user, group, or role. By auditing specific users, you can minimize the number of audit records generated. For information, see the examples under [Selecting SQL Statements to Audit](../05_edb_audit_logging/02_selecting_sql_statements_to_audit/#selecting_sql_statements_to_audit). + The following section describes selection of specific SQL statements for auditing using the `edb_audit_statement` parameter. diff --git a/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx b/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx index c56d7cf27e7..c2c30beecef 100644 --- a/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx +++ b/product_docs/docs/epas/12/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx @@ -279,7 +279,7 @@ The following is an example where `edb_audit_connect` and `edb_audit_statement` ```text edb_audit_connect = 'all' -edb_audit_statement = create view,create materialized view,create sequence,grant' +edb_audit_statement = 'create view,create materialized view,create sequence,grant' ``` Thus, only SQL statements invoked by the `CREATE VIEW`, `CREATE MATERIALIZED VIEW`, `CREATE SEQUENCE` and `GRANT` commands are audited. @@ -373,6 +373,206 @@ The `CREATE VIEW` and `CREATE MATERIALIZED VIEW` statements are audited. Note th The `CREATE SEQUENCE` and `GRANT` statements are audited since those values are included in the `edb_audit_statement` parameter. +**Example 3** + +The following is an example where `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values: + +```text +logging_collector = 'on' +edb_audit_connect = 'all' +edb_audit_statement = 'none' +``` + +The session for users who connect as `ADMIN` or `SYSDBA` can be fully audited. An admin user is connected to a database `auditdb` as `ADMINUSER`, the following `ALTER USER` command specifies that `ADMINUSER` is to be audited. + +```text +ALTER USER adminuser SET edb_audit_statement = "all"; +``` + +Setting the `edb_audit_statement` parameter to `all` allows auditing all of the SQL statements for an admin user. + +The database session that occurs is the following: + +```text +$ psql auditdb adminuser +Password for user adminuser: +psql.bin (12.0.0) +Type "help" for help. + +auditdb=# SHOW edb_audit_connect; + edb_audit_connect +------------------- + all +(1 row) + +auditdb=# SHOW edb_audit_statement; + edb_audit_statement +--------------------- + all +(1 row) + +auditdb=# SET search_path TO edb; +SET +auditdb=> CREATE TABLE dept +auditdb-> (deptno NUMBER(2), +auditdb(> dname VARCHAR2(14), +auditdb(> loc VARCHAR2(13) ); +CREATE TABLE +auditdb=> INSERT INTO dept VALUES (10, 'ACCOUNTING', 'NEW YORK'); +INSERT 0 1 +auditdb=> INSERT INTO dept VALUES (20, 'RESEARCH', 'DALLAS'); +INSERT 0 1 +auditdb=> INSERT INTO dept VALUES (30, 'SALES', 'CHICAGO'); +INSERT 0 1 +auditdb=> UPDATE dept SET loc = 'BEDFORD' WHERE deptno = 20; +UPDATE 1 +auditdb=> SELECT * FROM dept; + deptno | dname | loc +--------+------------+---------- + 10 | ACCOUNTING | NEW YORK + 30 | SALES | CHICAGO + 20 | RESEARCH | BEDFORD +(3 rows) + +auditdb=> DELETE FROM emp WHERE deptno = 40; +ERROR: relation "emp" does not exist +LINE 1: DELETE FROM emp WHERE deptno = 40; + ^ +auditdb=> DELETE FROM dept WHERE deptno = 10; +DELETE 1 +auditdb=> SELECT * FROM dept; + deptno | dname | loc +--------+----------+--------- + 30 | SALES | CHICAGO + 20 | RESEARCH | BEDFORD +(2 rows) +``` + +The resulting audit log file contains the following. + +Each audit log entry has been split and displayed across multiple lines, and a blank line has been inserted between the audit log entries for more clarity in the appearance of the results. + +```text +2021-06-23 06:06:59.027 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,1,"authentication",2021-06-23 06:06:59 IST,4/19,0,AUDIT,00000,"connection authorized: +user=adminuser database=auditdb",,,,,,,,,"","client backend",,"","","connect" + +2021-06-23 06:07:33.192 IST,"adminuser","auditdb",66316,"[local]",60daab0c. +1030c,2,"idle",2021-06-23 06:07:33 IST,4/16,0,AUDIT,00000,"statement: SHOW edb_audit_connect; +",,,,,,,,,"psql","client backend",,"SHOW","","sql statement" + +2021-06-23 06:08:12.474 IST,"adminuser","auditdb",66316,"[local]",60daab0c. +1030c,3,"idle",2021-06-23 06:08:12 IST,4/17,0,AUDIT,00000,"statement: SHOW edb_audit_statement; +",,,,,,,,,"psql","client backend",,"SHOW","","sql statement" + +2021-06-23 06:08:20.519 IST,"adminuser","auditdb",66922,"[local]",60dab036. +1056a,4,"idle",2021-06-23 06:08:20 IST,4/15,0,AUDIT,00000,"statement: SET search_path TO edb; +",,,,,,,,,"psql","client backend",,"SET","","set" + +2021-06-23 06:09:27.613 IST,"adminuser","auditdb",60218,"[local]",60dab117. +10602,5,"idle",2021-06-23 06:09:59 IST,4/21,0,AUDIT,00000,"statement: CREATE TABLE dept + (deptno NUMBER(2), + dname VARCHAR2(14), + loc VARCHAR2(13) );",,,,,,,,,"psql","client backend",,"CREATE TABLE","","create" + +2021-06-23 06:09:39.238 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,6,"idle",2021-06-23 06:09:29 IST,4/22,0,AUDIT,00000,"statement: INSERT INTO +dept VALUES (10, 'ACCOUNTING', 'NEW YORK');",,,,,,,,,"psql","client backend",,"INSERT","","insert" + +2021-06-23 06:09:39.242 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,7,"idle",2021-06-23 06:09:29 IST,4/23,0,AUDIT,00000,"statement: INSERT INTO +dept VALUES (20, 'RESEARCH', 'DALLAS');",,,,,,,,,"psql","client backend",,"INSERT","","insert" + +2021-06-23 06:09:39.247 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,8,"idle",2021-06-23 06:08:35 IST,4/24,0,AUDIT,00000,"statement: INSERT INTO +dept VALUES (30, 'SALES', 'CHICAGO');",,,,,,,,,"psql","client backend",,"INSERT","","insert" + +2021-06-23 06:10:04.849 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,9,"idle",2021-06-23 06:08:59 IST,4/25,0,AUDIT,00000,"statement: UPDATE dept SET loc = 'BEDFORD' +WHERE deptno = 20;",,,,,,,,,"psql","client backend",,"UPDATE","","update" + +2021-06-23 06:10:16.045 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,10,"idle",2021-06-23 06:08:59 IST,4/26,0,AUDIT,00000,"statement: SELECT * FROM dept;",,,,,,,,, +"psql","client backend",,"SELECT","","select" + +2021-06-23 06:10:40.593 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,11,"idle",2021-06-23 06:08:59 IST,4/27,0,AUDIT,00000,"statement: DELETE FROM emp WHERE deptno = 40; +",,,,,,,,,"psql","client backend",,"DELETE","","delete" + +2021-06-23 06:10:40.594 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,12,"DELETE",2021-06-23 06:08:59 IST,4/27,0,ERROR,42P01,"relation ""emp"" does not exist",,,,,, +"DELETE FROM emp WHERE deptno = 40;",13,,"psql","client backend",,"DELETE","","error" + +2021-06-23 06:11:02.563 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,13,"idle",2021-06-23 06:08:59 IST,4/28,0,AUDIT,00000,"statement: DELETE FROM dept WHERE deptno = 10; +",,,,,,,,,"psql","client backend",,"DELETE","","delete" + +2021-06-23 06:11:14.585 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,14,"idle",2021-06-23 06:08:59 IST,4/29,0,AUDIT,00000,"statement: SELECT * FROM dept;",,,,,,,,, +"psql","client backend",,"SELECT","","select" +``` + +**Example 4** + +The following is an example where `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values: + +```text +logging_collector = 'on' +edb_audit_connect = 'all' +edb_audit_statement = 'all' +``` + +The audit session for a user `carol` can be fully blocked by the database administrators using the `ALTER USER` command: + +```text +ALTER USER carol SET edb_audit_statement = "none"; +``` + +!!! Note + The database administrator can allow a specific user to audit any SQL statements by specifying the `ALTER USER` command and setting the `edb_audit_statement parameter` to any desired value. + +The database session that occurs is the following: + +```text +$ psql auditdb carol +Password for user carol: +psql.bin (12.0.0) +Type "help" for help. + +auditdb=# SHOW edb_audit_connect; + edb_audit_connect +------------------- + all +(1 row) + +auditdb=# SHOW edb_audit_statement; + edb_audit_statement +--------------------- + none +(1 row) + +auditdb=# SET search_path TO edb; +SET +auditdb=> CREATE TABLE salgrade +auditdb-> (grade NUMBER, +auditdb(> losal NUMBER, +auditdb(> hisal NUMBER); +CREATE TABLE +INSERT INTO salgrade VALUES (1, 700, 1200); +INSERT INTO salgrade VALUES (2, 1201, 1400); +INSERT INTO salgrade VALUES (3, 1401, 2000); +``` + +The resulting audit log file contains only the connection authentication information. Setting the `edb_audit_statement` parameter to `none` does not allow auditing any of the SQL statements for `carol`, and thereby no audit logs are generated. + +Each audit log entry has been split and displayed across multiple lines, and a blank line has been inserted between the audit log entries for more clarity in the appearance of the results. + +```text +2021-06-29 02:27:26.240 IST,"carol","auditdb",68072,"[local]",60dabd4e. +109e8,1,"authentication",2021-06-29 02:27:26 IST,4/13,0,AUDIT,00000,"connection authorized: user=carol +database=auditdb",,,,,,,,,"","client backend",,"","","connect" +``` + ## Data Manipulation Language Statements This section describes the values that can be included in the `edb_audit_statement` parameter to audit DML statements. diff --git a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx index e41dd2df8ea..89228af4010 100644 --- a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx +++ b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx @@ -47,7 +47,7 @@ The EDB Postgres pgAdmin 4 provides a powerful graphical interface for database The `--enable_acledit 1` option instructs the installer to grant permission to the user specified by the `--serviceaccount` option to access the Advanced Server binaries and `data` directory. By default, this option is disabled if `--enable_acledit 0` is specified or if the `--enable_acledit` option is completely omitted. !!! Note - Specification of this option is valid only when installing on Windows. The `--enable_acledit 1` option should be specified when a `discretionary access control list` (DACL) needs to be set for allowing access to objects on which Advanced Server is to be installed. See the following for information on a DACL: ).aspx + Specification of this option is valid only when installing on Windows. The `--enable_acledit 1` option should be specified when a `discretionary access control list` (DACL) needs to be set for allowing access to objects on which Advanced Server is to be installed. See the following for information on a DACL: https://msdn.microsoft.com/en-us/library/windows/desktop/aa446597(v=vs.85).aspx In order to perform future operations such as upgrading Advanced Server, access to the `data` directory must exist for the service account user specified by the `--serviceaccount` option. By specifying the `--enable_acledit 1` option, access to the `data` directory by the service account user is provided. diff --git a/product_docs/docs/epas/12/language_pack/01_supported_database_server_versions.mdx b/product_docs/docs/epas/12/language_pack/01_supported_database_server_versions.mdx index 9e2df4d290a..eb8ab553ca9 100644 --- a/product_docs/docs/epas/12/language_pack/01_supported_database_server_versions.mdx +++ b/product_docs/docs/epas/12/language_pack/01_supported_database_server_versions.mdx @@ -15,4 +15,4 @@ Language Pack installers are version and platform specific. Select the Language | Windows (64-bit) | PostgreSQL `9.6`,`10`,`11`,`12` | 1.0 | Perl `5.26`, Python `3.7`, Tcl `8.8` | | Windows (64-bit) | EDB Postgres Advanced Server `9.6`,`10`,`11`,`12` | 1.0 | Perl `5.26`, Python `3.7`, Tcl `8.6` | -For detailed information, please see the EDB Postgres Advanced Server Installation Guide for Linux, available at the [EDB website](/epas/12/). +For detailed information, please see the *EDB Postgres Advanced Server Installation Guide*, available at the [EDB website](/epas/12/). diff --git a/product_docs/docs/epas/12/language_pack/02_installing_language_pack.mdx b/product_docs/docs/epas/12/language_pack/02_installing_language_pack.mdx index b6f911fa6cc..d7a6fc5ae00 100644 --- a/product_docs/docs/epas/12/language_pack/02_installing_language_pack.mdx +++ b/product_docs/docs/epas/12/language_pack/02_installing_language_pack.mdx @@ -18,13 +18,13 @@ Assume Administrator privileges, and double-click the installer icon; if prompte ![The Language Selection Window](images/language1.png) -Fig. 1: The Language Selection Window +
Fig. 1: The Language Selection Window
The Language Pack setup wizard welcome window opens. ![The Language Pack Welcome Window](images/Welcome.png) -Fig. 2: The Language Pack Welcome Window +
Fig. 2: The Language Pack Welcome Window
Click `Next` to continue. @@ -36,7 +36,7 @@ The Ready to Install window displays the Language Pack installation directory: ![The Ready to Install dialog](images/ready_to_install_1.png) -Fig. 3: The Ready to Install dialog +
Fig. 3: The Ready to Install dialog
You cannot modify the installation directory. Click `Next` to continue. @@ -44,7 +44,7 @@ A progress bar marks installation progress. ![The Installing dialog](images/the_installing_dialog1.png) -Fig. 4: The Installing dialog +
Fig. 4: The Installing dialog
Click `Next` to continue. @@ -52,7 +52,7 @@ The installer will inform you that the Language Pack installation has completed; ![The Language Pack Setup Complete dialog](images/completed.png) -Fig. 5: The Language Pack Setup Complete dialog +
Fig. 5: The Language Pack Setup Complete dialog
### Installing Language Pack with Stack Builder @@ -70,7 +70,7 @@ Select your server from the drop-down menu on the Stack Builder Welcome window a ![The Stack Builder Welcome Window](images/stackbuilder.png) -Fig. 6: The Stack Builder Welcome Window +
Fig. 6: The Stack Builder Welcome Window
Expand the `Add-ons, tools and utilities` node of the `Categories` tree control, and check the box next to EDB Language Pack version. Click `Next` to continue. diff --git a/product_docs/docs/epas/12/language_pack/04_uninstalling_language_pack.mdx b/product_docs/docs/epas/12/language_pack/04_uninstalling_language_pack.mdx index c51775b8303..615c6b35736 100644 --- a/product_docs/docs/epas/12/language_pack/04_uninstalling_language_pack.mdx +++ b/product_docs/docs/epas/12/language_pack/04_uninstalling_language_pack.mdx @@ -12,10 +12,12 @@ Perform the following steps to uninstall Language Pack: ![The Language Pack Uninstaller](images/uninstall_lp1.png) -Fig. 1: The Language Pack Uninstaller +
Fig. 1: The Language Pack Uninstaller
2. The uninstallation process begins. Click `OK` when the uninstallation completes. ![Uninstalling Language Pack](images/uninstall_lp2.png) -Fig. 2: Uninstalling Language Pack +
Fig. 2: Uninstalling Language Pack
+ + diff --git a/product_docs/docs/epas/13/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/13/epas_compat_tools_guide/02_edb_loader.mdx index f6218e312ea..060bf98b850 100644 --- a/product_docs/docs/epas/13/epas_compat_tools_guide/02_edb_loader.mdx +++ b/product_docs/docs/epas/13/epas_compat_tools_guide/02_edb_loader.mdx @@ -157,7 +157,7 @@ Where `ENV_VARIABLE` is the environment variable that is set to the directory pa The `EDBLDR_ENV_STYLE` environment variable instructs Advanced Server to interpret environment variable references as Windows-styled references or Linux-styled references irregardless of the operating system on which EDB\*Loader resides. You can use this environment variable to create portable control files for EDB\*Loader. - On a Windows system, set `EDBLDR_ENV_STYLE` to `linux` or `unix` to instruct Advanced Server to recognize Linux-style references within the control file. -- On a Linux system, set `EDBLDR_ENV_STYLE` to windows to instruct Advanced Server to recognize Windows-style references within the control file. +- On a Linux system, set `EDBLDR_ENV_STYLE` to `windows` to instruct Advanced Server to recognize Windows-style references within the control file. The operating system account `enterprisedb` must have read permission on the directory and file specified by `data_file`. @@ -404,11 +404,8 @@ If the `FIELDS TERMINATED BY` clause is specified, then the `POSITION (start:end ``` CHAR [()] | DATE [()] | TIMESTAMP [()] [ "" ] | - INTEGER EXTERNAL [()] | - FLOAT EXTERNAL [()] | DECIMAL EXTERNAL [()] | - ZONED EXTERNAL [()] | ZONED [([,])] ``` @@ -528,7 +525,7 @@ The following is the corresponding delimiter-separated data file: 9104,"JONES, JR.",MANAGER,7839,02-APR-09,7975.00,20 ``` -The use of the `TRAILING NULLCOLS` clause allows the last field supplying the comm column to be omitted from the first and last records. The `comm` column is set to null for the rows inserted from these records. +The use of the `TRAILING NULLCOLS` clause allows the last field supplying the `comm` column to be omitted from the first and last records. The `comm` column is set to null for the rows inserted from these records. The double quotation mark enclosure character surrounds the value `JONES, JR.` in the last record since the comma delimiter character is part of the field value. @@ -761,7 +758,7 @@ SELECT * FROM emp WHERE empno > 9100; **NULLIF Clause** -The following example uses the `NULLIF` clause on the sal column to set it to null for employees of job `MANAGER` as well as on the comm column to set it to null if the employee is not a `SALESMAN` and is not in department `30`. In other words, a comm value is accepted if the employee is a `SALESMAN` or is a member of department `30`. +The following example uses the `NULLIF` clause on the `sal` column to set it to null for employees of job `MANAGER` as well as on the `comm` column to set it to null if the employee is not a `SALESMAN` and is not in department `30`. In other words, a `comm` value is accepted if the employee is a `SALESMAN` or is a member of department `30`. The following is the control file: diff --git a/product_docs/docs/epas/13/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx b/product_docs/docs/epas/13/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx index 56909a74c05..73f495c3585 100644 --- a/product_docs/docs/epas/13/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx +++ b/product_docs/docs/epas/13/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA.mdx @@ -1059,7 +1059,7 @@ function_name(, , , ) `scope` - scope determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: + `scope` determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: - `SYS` indicates that the function should return information about system defined tables. A table is considered a system table if it is stored in one of the following schemas: `pg_catalog`, `information_schema`, or `sys`. - `USER` indicates that the function should return information about user-defined tables. @@ -1186,7 +1186,7 @@ statio_tables_rpt(, , , ) `scope` - scope determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: + `scope` determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: - `SYS` indicates that the function should return information about system defined tables. A table is considered a system table if it is stored in one of the following schemas: `pg_catalog`, `information_schema`, or `sys`. - `USER` indicates that the function should return information about user-defined tables. @@ -1273,7 +1273,7 @@ stat_indexes_rpt(, , , ) `scope` - scope determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: + `scope` determines which tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`: - `SYS` indicates that the function should return information about system defined tables. A table is considered a system table if it is stored in one of the following schemas: `pg_catalog, information_schema`, or `sys`. - `USER` indicates that the function should return information about user-defined tables. diff --git a/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx index b0b83983c5a..acf53988888 100644 --- a/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx +++ b/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx @@ -28,7 +28,7 @@ The EDB\*Plus command line client provides a user interface to Advanced Server t - Execute OS commands - Record output -For detailed installation and usage information about EDB\*Plus, see the EDB\*Plus User's Guide, available from the EDB website at: +For detailed installation and usage information about EDB\*Plus, see the *EDB\*Plus User's Guide*, available from the EDB website at: [https://www.enterprisedb.com/docs/p/edbplus](/epas/latest/edb_plus/) diff --git a/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx b/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx index 915bd8080c6..4316544197d 100644 --- a/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx +++ b/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters.mdx @@ -229,7 +229,7 @@ The following table shows the summary of configuration parameters: | `log_temp_files` | Session | Immediate | Superuser | Log the use of temporary files larger than this number of kilobytes. | | | `log_timezone` | Cluster | Reload | EPAS service account | Sets the time zone to use in log messages. | | | `log_truncate_on_rotation` | Cluster | Reload | EPAS service account | Truncate existing log files of same name during log rotation. | | -| `logging_collector` | Cluster | Restart | EPAS service account | Start a subprocess to capture stderr output and/or csvlogs into log files. | | +| `logging_collector` | Cluster | Restart | EPAS service account | Start a subprocess to capture stderr output and/or csv logs into log files. | | | `maintenance_work_mem` | Session | Immediate | User | Sets the maximum memory to be used for maintenance operations. | | | `max_connections` | Cluster | Restart | EPAS service account | Sets the maximum number of concurrent connections. | | | `max_files_per_process` | Cluster | Restart | EPAS service account | Sets the maximum number of simultaneously open files for each server process. | | diff --git a/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx b/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx index 63661a8cf08..d559c095825 100644 --- a/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx +++ b/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters.mdx @@ -60,4 +60,7 @@ Use the following configuration parameters to control database auditing. See [Su Set to `syslog` to use the syslog process and its location as configured in the `/etc/syslog.conf` file. The `syslog` setting is valid for Advanced Server running on a Linux host and is not supported on Windows systems. **Note:** In recent Linux versions, syslog has been replaced by `rsyslog` and the configuration file is in `/etc/rsyslog.conf`. +!!! Note + Advanced Server allows administrative users associated with administrative privileges to audit statements by any user, group, or role. By auditing specific users, you can minimize the number of audit records generated. For information, see the examples under [Selecting SQL Statements to Audit](../05_edb_audit_logging/02_selecting_sql_statements_to_audit/#selecting_sql_statements_to_audit). + The following section describes selection of specific SQL statements for auditing using the `edb_audit_statement` parameter. diff --git a/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx b/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx index a77b5b27a01..05357430436 100644 --- a/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx +++ b/product_docs/docs/epas/13/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx @@ -286,7 +286,7 @@ The following is an example where `edb_audit_connect` and `edb_audit_statement` ```text logging_collector = 'on' edb_audit_connect = 'all' -edb_audit_statement = create view,create materialized view,create sequence,grant' +edb_audit_statement = 'create view,create materialized view,create sequence,grant' ``` Thus, only SQL statements invoked by the `CREATE VIEW`, `CREATE MATERIALIZED VIEW`, `CREATE SEQUENCE` and `GRANT` commands are audited. @@ -380,6 +380,206 @@ The `CREATE VIEW` and `CREATE MATERIALIZED VIEW` statements are audited. Note th The `CREATE SEQUENCE` and `GRANT` statements are audited since those values are included in the `edb_audit_statement` parameter. +**Example 3** + +The following is an example where `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values: + +```text +logging_collector = 'on' +edb_audit_connect = 'all' +edb_audit_statement = 'none' +``` + +The session for users who connect as `ADMIN` or `SYSDBA` can be fully audited. An admin user is connected to a database `auditdb` as `ADMINUSER`, the following `ALTER USER` command specifies that `ADMINUSER` is to be audited. + +```text +ALTER USER adminuser SET edb_audit_statement = "all"; +``` + +Setting the `edb_audit_statement` parameter to `all` allows auditing all of the SQL statements for an admin user. + +The database session that occurs is the following: + +```text +$ psql auditdb adminuser +Password for user adminuser: +psql.bin (13.0.0) +Type "help" for help. + +auditdb=# SHOW edb_audit_connect; + edb_audit_connect +------------------- + all +(1 row) + +auditdb=# SHOW edb_audit_statement; + edb_audit_statement +--------------------- + all +(1 row) + +auditdb=# SET search_path TO edb; +SET +auditdb=> CREATE TABLE dept +auditdb-> (deptno NUMBER(2), +auditdb(> dname VARCHAR2(14), +auditdb(> loc VARCHAR2(13) ); +CREATE TABLE +auditdb=> INSERT INTO dept VALUES (10, 'ACCOUNTING', 'NEW YORK'); +INSERT 0 1 +auditdb=> INSERT INTO dept VALUES (20, 'RESEARCH', 'DALLAS'); +INSERT 0 1 +auditdb=> INSERT INTO dept VALUES (30, 'SALES', 'CHICAGO'); +INSERT 0 1 +auditdb=> UPDATE dept SET loc = 'BEDFORD' WHERE deptno = 20; +UPDATE 1 +auditdb=> SELECT * FROM dept; + deptno | dname | loc +--------+------------+---------- + 10 | ACCOUNTING | NEW YORK + 30 | SALES | CHICAGO + 20 | RESEARCH | BEDFORD +(3 rows) + +auditdb=> DELETE FROM emp WHERE deptno = 40; +ERROR: relation "emp" does not exist +LINE 1: DELETE FROM emp WHERE deptno = 40; + ^ +auditdb=> DELETE FROM dept WHERE deptno = 10; +DELETE 1 +auditdb=> SELECT * FROM dept; + deptno | dname | loc +--------+----------+--------- + 30 | SALES | CHICAGO + 20 | RESEARCH | BEDFORD +(2 rows) +``` + +The resulting audit log file contains the following. + +Each audit log entry has been split and displayed across multiple lines, and a blank line has been inserted between the audit log entries for more clarity in the appearance of the results. + +```text +2021-06-23 06:06:59.027 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,1,"authentication",2021-06-23 06:06:59 IST,4/19,0,AUDIT,00000,"connection authorized: +user=adminuser database=auditdb",,,,,,,,,"","client backend",,"","","connect" + +2021-06-23 06:07:33.192 IST,"adminuser","auditdb",66316,"[local]",60daab0c. +1030c,2,"idle",2021-06-23 06:07:33 IST,4/16,0,AUDIT,00000,"statement: SHOW edb_audit_connect; +",,,,,,,,,"psql","client backend",,"SHOW","","sql statement" + +2021-06-23 06:08:12.474 IST,"adminuser","auditdb",66316,"[local]",60daab0c. +1030c,3,"idle",2021-06-23 06:08:12 IST,4/17,0,AUDIT,00000,"statement: SHOW edb_audit_statement; +",,,,,,,,,"psql","client backend",,"SHOW","","sql statement" + +2021-06-23 06:08:20.519 IST,"adminuser","auditdb",66922,"[local]",60dab036. +1056a,4,"idle",2021-06-23 06:08:20 IST,4/15,0,AUDIT,00000,"statement: SET search_path TO edb; +",,,,,,,,,"psql","client backend",,"SET","","set" + +2021-06-23 06:09:27.613 IST,"adminuser","auditdb",60218,"[local]",60dab117. +10602,5,"idle",2021-06-23 06:09:59 IST,4/21,0,AUDIT,00000,"statement: CREATE TABLE dept + (deptno NUMBER(2), + dname VARCHAR2(14), + loc VARCHAR2(13) );",,,,,,,,,"psql","client backend",,"CREATE TABLE","","create" + +2021-06-23 06:09:39.238 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,6,"idle",2021-06-23 06:09:29 IST,4/22,0,AUDIT,00000,"statement: INSERT INTO +dept VALUES (10, 'ACCOUNTING', 'NEW YORK');",,,,,,,,,"psql","client backend",,"INSERT","","insert" + +2021-06-23 06:09:39.242 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,7,"idle",2021-06-23 06:09:29 IST,4/23,0,AUDIT,00000,"statement: INSERT INTO +dept VALUES (20, 'RESEARCH', 'DALLAS');",,,,,,,,,"psql","client backend",,"INSERT","","insert" + +2021-06-23 06:09:39.247 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,8,"idle",2021-06-23 06:08:35 IST,4/24,0,AUDIT,00000,"statement: INSERT INTO +dept VALUES (30, 'SALES', 'CHICAGO');",,,,,,,,,"psql","client backend",,"INSERT","","insert" + +2021-06-23 06:10:04.849 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,9,"idle",2021-06-23 06:08:59 IST,4/25,0,AUDIT,00000,"statement: UPDATE dept SET loc = 'BEDFORD' +WHERE deptno = 20;",,,,,,,,,"psql","client backend",,"UPDATE","","update" + +2021-06-23 06:10:16.045 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,10,"idle",2021-06-23 06:08:59 IST,4/26,0,AUDIT,00000,"statement: SELECT * FROM dept;",,,,,,,,, +"psql","client backend",,"SELECT","","select" + +2021-06-23 06:10:40.593 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,11,"idle",2021-06-23 06:08:59 IST,4/27,0,AUDIT,00000,"statement: DELETE FROM emp WHERE deptno = 40; +",,,,,,,,,"psql","client backend",,"DELETE","","delete" + +2021-06-23 06:10:40.594 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,12,"DELETE",2021-06-23 06:08:59 IST,4/27,0,ERROR,42P01,"relation ""emp"" does not exist",,,,,, +"DELETE FROM emp WHERE deptno = 40;",13,,"psql","client backend",,"DELETE","","error" + +2021-06-23 06:11:02.563 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,13,"idle",2021-06-23 06:08:59 IST,4/28,0,AUDIT,00000,"statement: DELETE FROM dept WHERE deptno = 10; +",,,,,,,,,"psql","client backend",,"DELETE","","delete" + +2021-06-23 06:11:14.585 IST,"adminuser","auditdb",60218,"[local]",60d3083b. +eb3a,14,"idle",2021-06-23 06:08:59 IST,4/29,0,AUDIT,00000,"statement: SELECT * FROM dept;",,,,,,,,, +"psql","client backend",,"SELECT","","select" +``` + +**Example 4** + +The following is an example where `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values: + +```text +logging_collector = 'on' +edb_audit_connect = 'all' +edb_audit_statement = 'all' +``` + +The audit session for a user `carol` can be fully blocked by the database administrators using the `ALTER USER` command: + +```text +ALTER USER carol SET edb_audit_statement = "none"; +``` + +!!! Note + The database administrator can allow a specific user to audit any SQL statements by specifying the `ALTER USER` command and setting the `edb_audit_statement parameter` to any desired value. + +The database session that occurs is the following: + +```text +$ psql auditdb carol +Password for user carol: +psql.bin (13.0.0) +Type "help" for help. + +auditdb=# SHOW edb_audit_connect; + edb_audit_connect +------------------- + all +(1 row) + +auditdb=# SHOW edb_audit_statement; + edb_audit_statement +--------------------- + none +(1 row) + +auditdb=# SET search_path TO edb; +SET +auditdb=> CREATE TABLE salgrade +auditdb-> (grade NUMBER, +auditdb(> losal NUMBER, +auditdb(> hisal NUMBER); +CREATE TABLE +INSERT INTO salgrade VALUES (1, 700, 1200); +INSERT INTO salgrade VALUES (2, 1201, 1400); +INSERT INTO salgrade VALUES (3, 1401, 2000); +``` + +The resulting audit log file contains only the connection authentication information. Setting the `edb_audit_statement` parameter to `none` does not allow auditing any of the SQL statements for `carol`, and thereby no audit logs are generated. + +Each audit log entry has been split and displayed across multiple lines, and a blank line has been inserted between the audit log entries for more clarity in the appearance of the results. + +```text +2021-06-29 02:27:26.240 IST,"carol","auditdb",68072,"[local]",60dabd4e. +109e8,1,"authentication",2021-06-29 02:27:26 IST,4/13,0,AUDIT,00000,"connection authorized: user=carol +database=auditdb",,,,,,,,,"","client backend",,"","","connect" +``` + ## Data Manipulation Language Statements This section describes the values that can be included in the `edb_audit_statement` parameter to audit DML statements. diff --git a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx index 9f39d6401b1..2fb71a104e4 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options.mdx @@ -47,7 +47,7 @@ The EDB Postgres pgAdmin 4 provides a powerful graphical interface for database The `--enable_acledit 1` option instructs the installer to grant permission to the user specified by the `--serviceaccount` option to access the Advanced Server binaries and `data` directory. By default, this option is disabled if `--enable_acledit 0` is specified or if the `--enable_acledit` option is completely omitted. !!! Note - Specification of this option is valid only when installing on Windows. The `--enable_acledit 1` option should be specified when a `discretionary access control list` (DACL) needs to be set for allowing access to objects on which Advanced Server is to be installed. See the following for information on a DACL: ).aspx + Specification of this option is valid only when installing on Windows. The `--enable_acledit 1` option should be specified when a `discretionary access control list` (DACL) needs to be set for allowing access to objects on which Advanced Server is to be installed. See the following for information on a DACL: https://msdn.microsoft.com/en-us/library/windows/desktop/aa446597(v=vs.85).aspx In order to perform future operations such as upgrading Advanced Server, access to the `data` directory must exist for the service account user specified by the `--serviceaccount` option. By specifying the `--enable_acledit 1` option, access to the `data` directory by the service account user is provided. diff --git a/product_docs/docs/epas/13/language_pack/01_supported_database_server_versions.mdx b/product_docs/docs/epas/13/language_pack/01_supported_database_server_versions.mdx index ca058e9b8a3..08e185c4c18 100644 --- a/product_docs/docs/epas/13/language_pack/01_supported_database_server_versions.mdx +++ b/product_docs/docs/epas/13/language_pack/01_supported_database_server_versions.mdx @@ -21,4 +21,4 @@ Language Pack installers are version and platform specific. Select the Language | Windows (64-bit) | PostgreSQL `9.6`,`10`,`11`,`12`,`13` | 1.0 | Perl `5.26`, Python `3.7`, Tcl `8.8` | | Windows (64-bit) | EDB Postgres Advanced Server `9.6`,`10`,`11`,`12`,`13`| 1.0 | Perl `5.26`, Python `3.7`, Tcl `8.6` | -For detailed information, please see the EDB Postgres Advanced Server Installation Guide for Linux, available at the [EDB website](/epas/latest/). +For detailed information, please see the *EDB Postgres Advanced Server Installation Guide*, available at the [EDB website](/epas/latest/). diff --git a/product_docs/docs/epas/13/language_pack/02_installing_language_pack.mdx b/product_docs/docs/epas/13/language_pack/02_installing_language_pack.mdx index debb3deeb88..e3cfa8d8993 100644 --- a/product_docs/docs/epas/13/language_pack/02_installing_language_pack.mdx +++ b/product_docs/docs/epas/13/language_pack/02_installing_language_pack.mdx @@ -24,13 +24,13 @@ Assume Administrator privileges, and double-click the installer icon; if prompte ![The Language Selection Window](images/language1.png) -Fig. 1: The Language Selection Window +
Fig. 1: The Language Selection Window
The Language Pack setup wizard welcome window opens. ![The Language Pack Welcome Window](images/language_pack_welcome.png) -Fig. 2: The Language Pack Welcome Window +
Fig. 2: The Language Pack Welcome Window
Click `Next` to continue. @@ -42,7 +42,7 @@ The Ready to Install window displays the Language Pack installation directory: ![The Ready to Install dialog](images/lp.2_aug6.png) -Fig. 3: The Ready to Install dialog +
Fig. 3: The Ready to Install dialog
You cannot modify the installation directory. Click `Next` to continue. @@ -50,7 +50,7 @@ A progress bar marks installation progress. ![The Installing dialog](images/lp3_aug6.png) -Fig. 4: The Installing dialog +
Fig. 4: The Installing dialog
Click `Next` to continue. @@ -58,7 +58,7 @@ The installer will inform you that the Language Pack installation has completed; ![The Language Pack Setup Complete dialog](images/complete1.png) -Fig. 5: The Language Pack Setup Complete dialog +
Fig. 5: The Language Pack Setup Complete dialog
### Installing Language Pack with Stack Builder @@ -76,25 +76,25 @@ Select your server from the drop-down menu on the Stack Builder Welcome window a ![The Stack Builder Welcome Window](images/stackbuilder_welcome.png) -Fig. 6: The Stack Builder Welcome Window +
Fig. 6: The Stack Builder Welcome Window
Expand the `Add-ons, tools and utilities` node of the `Categories` tree control, and check the box next to `EDB Language Pack v1.0-5`. Click `Next` to continue. ![The Language Pack Selection Window](images/language_pack_versions_selection.png) -Fig. 7: The Language Pack Selection Window +
Fig. 7: The Language Pack Selection Window
Stack Builder will confirm your package selection before downloading the installer. Click `Next` to continue. - ![The Selected Packages Window](images/language_pack_selected_pacakges.png) +![The Selected Packages Window](images/language_pack_selected_pacakges.png) -Fig. 8: The Selected Packages Window +
Fig. 8: The Selected Packages Window
When the download completes, Stack Builder will offer to invoke the installer for you, or will delay the installation until a more convenient time. To invoke the installer, click `Next` and follow the steps provided in the [Invoking the Graphical Installer section](#invoking-the-graphical-installer). ![The Selected Packages Window](images/stackbuilder_installation_complete.png) -Fig. 9: The Selected Packages Window +
Fig. 9: The Selected Packages Window
## Configuring Language Pack diff --git a/product_docs/docs/epas/13/language_pack/03_using_the_procedural_languages.mdx b/product_docs/docs/epas/13/language_pack/03_using_the_procedural_languages.mdx index 5f62f3ff6dc..203cf131e03 100644 --- a/product_docs/docs/epas/13/language_pack/03_using_the_procedural_languages.mdx +++ b/product_docs/docs/epas/13/language_pack/03_using_the_procedural_languages.mdx @@ -129,4 +129,4 @@ tcl_max (1 row) ``` -For more information about using the Tcl procedural language, consult the official [PostgreSQL documentation](https://www.postgresql.org/docs/12/static/pltcl.html). +For more information about using the Tcl procedural language, consult the official [PostgreSQL documentation](https://www.postgresql.org/docs/13/static/pltcl.html). diff --git a/product_docs/docs/epas/13/language_pack/04_uninstalling_language_pack.mdx b/product_docs/docs/epas/13/language_pack/04_uninstalling_language_pack.mdx index 4e371d60ff8..7e136301f36 100644 --- a/product_docs/docs/epas/13/language_pack/04_uninstalling_language_pack.mdx +++ b/product_docs/docs/epas/13/language_pack/04_uninstalling_language_pack.mdx @@ -18,10 +18,12 @@ Perform the following steps to uninstall Language Pack: ![The Language Pack Uninstaller](images/uninstall_lp1.png) -Fig. 1: The Language Pack Uninstaller +
Fig. 1: The Language Pack Uninstaller
2. The uninstallation process begins. Click `OK` when the uninstallation completes. ![Uninstalling Language Pack](images/uninstall_lp2.png) -Fig. 2: Uninstalling Language Pack +
Fig. 2: Uninstalling Language Pack
+ + From 2a9f1f600b9aae502c6ac05cb1c60131acb78480 Mon Sep 17 00:00:00 2001 From: sheetal Date: Thu, 1 Jul 2021 15:59:55 +0530 Subject: [PATCH 2/3] Fixed the url Former-commit-id: dba2c0769de18bd9c8bc2d4a67c9995b13ed40e0 --- product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx | 2 +- product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx index fa2fdd7cae5..d9cb7c8f6ef 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx @@ -30,7 +30,7 @@ The EDB\*Plus command line client provides a user interface to Advanced Server t For detailed installation and usage information about EDB\*Plus, see the *EDB\*Plus User's Guide*, available from the EnterpriseDB website at: -[https://www.enterprisedb.com/docs/p/edbplus](/epas/latest/edb_plus/) +[https://www.enterprisedb.com/docs](/epas/latest/) For detailed information about the features supported by Advanced Server, consult the complete library of Advanced Server guides available at: diff --git a/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx index acf53988888..0cd3164aa09 100644 --- a/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx +++ b/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx @@ -30,7 +30,7 @@ The EDB\*Plus command line client provides a user interface to Advanced Server t For detailed installation and usage information about EDB\*Plus, see the *EDB\*Plus User's Guide*, available from the EDB website at: -[https://www.enterprisedb.com/docs/p/edbplus](/epas/latest/edb_plus/) +[https://www.enterprisedb.com/docs](/epas/latest/) For detailed information about the features supported by Advanced Server, consult the complete library of Advanced Server guides available at: From a480ccf950ba5a8c44a23b979bcc8d40a9bfb8fd Mon Sep 17 00:00:00 2001 From: sheetal Date: Thu, 1 Jul 2021 17:35:09 +0530 Subject: [PATCH 3/3] DB-142 hyperlink fixed Former-commit-id: 17d3477b94fd6f0e396ef6fd8324c28282b57fa7 --- product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx | 6 ++---- product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx | 4 +--- 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx index d9cb7c8f6ef..5fad4f391a1 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/index.mdx @@ -28,10 +28,8 @@ The EDB\*Plus command line client provides a user interface to Advanced Server t - Execute OS commands - Record output -For detailed installation and usage information about EDB\*Plus, see the *EDB\*Plus User's Guide*, available from the EnterpriseDB website at: - -[https://www.enterprisedb.com/docs](/epas/latest/) +For detailed installation and usage information about EDB\*Plus, see the [EDB\*Plus User's Guide](https://www.enterprisedb.com/docs/epas/12/edb_plus/) available from EnterpriseDB website. For detailed information about the features supported by Advanced Server, consult the complete library of Advanced Server guides available at: -[https://www.enterprisedb.com/docs](/epas/latest/) +[https://www.enterprisedb.com/docs](/epas/12/) diff --git a/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx index 0cd3164aa09..1d145a6c0e0 100644 --- a/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx +++ b/product_docs/docs/epas/13/epas_compat_tools_guide/index.mdx @@ -28,9 +28,7 @@ The EDB\*Plus command line client provides a user interface to Advanced Server t - Execute OS commands - Record output -For detailed installation and usage information about EDB\*Plus, see the *EDB\*Plus User's Guide*, available from the EDB website at: - -[https://www.enterprisedb.com/docs](/epas/latest/) +For detailed installation and usage information about EDB\*Plus, see the [EDB\*Plus User's Guide](https://www.enterprisedb.com/docs/epas/latest/edb_plus/) available from EDB website. For detailed information about the features supported by Advanced Server, consult the complete library of Advanced Server guides available at: