diff --git a/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx b/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx index 850c078e4b2..501475436d2 100644 --- a/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx +++ b/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx @@ -48,7 +48,7 @@ sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs) The command `lsb_release -cs` retrieves the name of the installed OS version, in this case "bionic" - this ensures that we're pulling from the correct repository for this release of the operating system. Supported releases can be found on [the PostgreSQL wiki](https://wiki.postgresql.org/wiki/Apt). The resulting [sources file](https://wiki.debian.org/SourcesList) looks like this: -```output +```console deb http://apt.postgresql.org/pub/repos/apt/ bionic-pgdg main ``` @@ -72,7 +72,7 @@ If you desired a version other than the latest, you'd specify that instead - for The Ubuntu installation script runs [`initdb`](https://www.postgresql.org/docs/current/app-initdb.html) to configure the default database cluster. You'll see this within the output once the cluster has been initialized: -```output +```console Success. You can now start the database server using: pg_ctlcluster 12 main start @@ -80,7 +80,7 @@ Success. You can now start the database server using: Don't actually run that though; the installation script also configures and starts services to automatically, as you can see from the rest of the installation output: -```output +```console Ver Cluster Port Status Owner Data directory Log file 12 main 5432 down postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log update-alternatives: using /usr/share/postgresql/12/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode diff --git a/gatsby-config.js b/gatsby-config.js index bd5c03d63a0..0d717cf07a3 100644 --- a/gatsby-config.js +++ b/gatsby-config.js @@ -292,6 +292,7 @@ module.exports = { postgresql: "sql", sh: "shell", "c++": "cpp", + console: "shell-session", }, }, }, diff --git a/product_docs/docs/biganimal/release/overview/03_security/compliance_and_certifications.mdx b/product_docs/docs/biganimal/release/overview/03_security/compliance_and_certifications.mdx index 9077f85e0e0..5e2844b65e4 100644 --- a/product_docs/docs/biganimal/release/overview/03_security/compliance_and_certifications.mdx +++ b/product_docs/docs/biganimal/release/overview/03_security/compliance_and_certifications.mdx @@ -28,3 +28,10 @@ The General Data Protection Regulation (GDPR) is a regulation in European Union GDPR compliance implies both privacy and security mechanisms definition, enforcement, and control, including evidence collection. BigAnimal supports GDPR at service level, which means BigAnimal protects the personal data and privacy of EU citizens. +## PCI DSS + + The Payment Card Industry Data Security Standard (PCI DSS) is a set of security standards designed to ensure that companies that accept, process, store, or transmit credit card information maintain a secure environment. See the [PCI Security Council](https://www.pcisecuritystandards.org/) website for more information about PCI. + + BigAnimal is compliant with PCI. A PCI Qualified Security Assessor (QSA) certifies compliance. To achieve compliance with PCI DSS on a BigAnimal cluster, any information related to payments or other personally-identifiable information (PII) must be encrypted, tokenized, or masked before being written to BigAnimal. You can do this from within your customer application or through a third-party solution such as Satori. + + Contact your EDB sales representative if you want to learn more about achieving PCI DSS compliance with your BigAnimal clusters. diff --git a/product_docs/docs/biganimal/release/using_cluster/terraform_provider.mdx b/product_docs/docs/biganimal/release/using_cluster/terraform_provider.mdx index 19fddf4f9da..fb9df2f8198 100644 --- a/product_docs/docs/biganimal/release/using_cluster/terraform_provider.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/terraform_provider.mdx @@ -22,7 +22,7 @@ To use Terraform with BigAnimal, you need: ## Example usage -```terraform +```hcl # Configure the BigAnimal Provider provider "biganimal" { ba_bearer_token = "" diff --git a/product_docs/docs/epas/15/epas_compat_reference/02_the_sql_language/03_functions_and_operators/11_aggregate_functions.mdx b/product_docs/docs/epas/15/epas_compat_reference/02_the_sql_language/03_functions_and_operators/11_aggregate_functions.mdx index a5279a22b36..87194f90c23 100644 --- a/product_docs/docs/epas/15/epas_compat_reference/02_the_sql_language/03_functions_and_operators/11_aggregate_functions.mdx +++ b/product_docs/docs/epas/15/epas_compat_reference/02_the_sql_language/03_functions_and_operators/11_aggregate_functions.mdx @@ -88,7 +88,7 @@ The `LISTAGG` function returns a string value. This example concatenates the values in the `emp` table and lists all the employees separated by a `delimiter` comma. First, create a table named `emp`. Then insert records into the `emp` table. -```texsql +```sql edb=# CREATE TABLE emp edb-# (EMPNO NUMBER(4) NOT NULL, edb(# ENAME VARCHAR2(10), diff --git a/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx b/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx index 0ce27bc3fe6..20a1842cdbe 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx @@ -184,6 +184,11 @@ Before you begin, configure the client for SSL with trigger mode. The default location of these files is `{user.home}/.postgresql(e.g/var/lib/edb/.postgresql/)`. The file location can be overridden using SSL connection parameters or Postgres SSL environmental variables, see [Setting Non-default Paths using Environment Variables](#setting-non-default-paths-using-environment-variables) for more information. + !!!note + If you used the Linux interactive installer, and set the operating system username as: + - `postgres`, your `{user.home}` path is `/var/lib/pgsql/` + - `enterprisedb`, your `{user.home}` path is `/var/lib/edb/`, which is the same path created from an RPM installation. + Copy and rename the files: ``` $ cd /var/lib/pgsql/.postgresql/ diff --git a/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx b/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx index 6f3bcead206..b01b9cc1ca3 100644 --- a/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx +++ b/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx @@ -93,7 +93,7 @@ __OUTPUT__ On `MMRnode_c` the conflicting row inserted on this node remains along with the updates performed on this node: -```shql +```sql MMRnode_c=# SELECT * FROM emp; __OUTPUT__ empno | ename | job | mgr | hiredate | sal | comm | deptno diff --git a/product_docs/docs/pem/8/pem_online_help/pem_worker_usage_guide.mdx b/product_docs/docs/pem/8/pem_online_help/pem_worker_usage_guide.mdx index 194a79f56c3..c835b9b2674 100644 --- a/product_docs/docs/pem/8/pem_online_help/pem_worker_usage_guide.mdx +++ b/product_docs/docs/pem/8/pem_online_help/pem_worker_usage_guide.mdx @@ -9,155 +9,154 @@ The PEM Worker performs tasks on behalf of the PEM Agent. Please note that all t The following command-line options are supported by the PEM Worker: -- On Linux: - - ```console - $./pemworker - Postgres Enterprise Manager Agent - Version: 8.0.0 - (Revision: REL-7_15_0-5-685-g415f794, Built on: Dec 1 2020 13:27:02) - Schema Supported: 202010081 - - ./pemworker [options] - ./pemworker --register-agent [register-options] - ./pemworker --register-server [register-server-options] - ./pemworker --unregister-server [unregister-server-options] - ./pemworker --unregister-agent [unregister-agent-options] - ./pemworker --add-webhook [add-webhook-options] - ./pemworker --remove-webhook [remove-webhook-options] - ./pemworker --register-barman [barman-registration-options] - ./pemworker --update-barman [barman-update-options] - ./pemworker --unregister-barman [barman-unregistration-options] - - - options: - -v/--version (Show the version & the supported schema and, then exit.) - -c (Path to the configuration file.) - -o