diff --git a/.github/workflows/tools-events.yml b/.github/workflows/tools-events.yml new file mode 100644 index 00000000000..cb82583a910 --- /dev/null +++ b/.github/workflows/tools-events.yml @@ -0,0 +1,46 @@ +name: Forward key events to the docs-tools repository +on: + pull_request: + push: + create: + delete: + release: +jobs: + dispatch-events: + runs-on: ubuntu-latest + steps: + - name: Create event name + run: | + EVENT_PREFIX="docs-${GITHUB_REPOSITORY//\//-}" + echo EVENT_PREFIX="${EVENT_PREFIX@L}" >> $GITHUB_ENV + - name: Repository Dispatch + uses: peter-evans/repository-dispatch@v3 + with: + token: ${{ secrets.TOOLS_EVENT_SYNC_PAT }} + repository: enterprisedb/docs-tools + event-type: ${{ env.EVENT_PREFIX }}-${{ github.event_name }} + client-payload: | + { + "ref": "${{ github.head_ref || github.ref }}", + "ref_type": "${{ github.ref_type }}", + "ref_name": "${{ github.ref_name }}", + "repo": "${{ github.repository }}", + "sha": "${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}", + "type": "${{ github.event_name }}", + "push": { + "before": "${{ github.event.before || '' }}", + "after": "${{ github.event.after || '' }}", + "created": "${{ github.event.created || false }}", + "deleted": "${{ github.event.deleted || false }}" + }, + "action": "${{ github.event.action }}", + "number": "${{ github.event.number }}", + "release": { + "tag_name": "${{ github.event.release && github.event.release.tag_name || '' }}", + "id": "${{ github.event.release && github.event.release.id || '' }}", + "tag": "${{ github.event.release && github.event.release.tag_name || '' }}", + "name": "${{ github.event.release && github.event.release.name || '' }}", + "body": "${{ github.event.release && github.event.release.body || '' }}", + "draft": "${{ github.event.release && github.event.release.draft || false }}" + } + } diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/installing/complete.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/installing/complete.mdx index 68134794ba8..7c86340cea9 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/installing/complete.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/installing/complete.mdx @@ -11,9 +11,37 @@ The AI Database extension provides a set of functions to run AI/ML models in the ```sql ebd=# CREATE EXTENSION aidb CASCADE; +__OUTPUT__ NOTICE: installing required extension "vector" CREATE EXTENSION -edb=# +``` + +#### Additional steps for EDB Postgres Distributed (PGD) +A manual step is required to set up replication within the PGD cluster for the AIDB extension catalog tables: + +```sql +bdrdb=# SELECT aidb.bdr_setup(); +__OUTPUT__ + bdr_setup +----------- + +(1 row) +``` + +You can confirm that the AIDB tables are part of the desired replication set using this SQL command: +```sql +bdrdb=# select * from bdr.tables where nspname='aidb'; +__OUTPUT__ + relid | nspname | relname | set_name | set_ops | rel_columns | row_filter | conflict_detection +-------+---------+---------------------------------------+----------------+---------------------------------+-------------+------------+-------------------- + 18281 | aidb | pipeline_runtime_state | p-2y7357q195-a | {INSERT,UPDATE,DELETE,TRUNCATE} | | | row_origin + 18354 | aidb | preparer_registry | p-2y7357q195-a | {INSERT,UPDATE,DELETE,TRUNCATE} | | | row_origin + 18363 | aidb | preparer_registry_source_table | p-2y7357q195-a | {INSERT,UPDATE,DELETE,TRUNCATE} | | | row_origin + 18375 | aidb | preparer_registry_source_volume | p-2y7357q195-a | {INSERT,UPDATE,DELETE,TRUNCATE} | | | row_origin + 18430 | aidb | knowledge_base_registry | p-2y7357q195-a | {INSERT,UPDATE,DELETE,TRUNCATE} | | | row_origin + 18440 | aidb | knowledge_base_registry_source_table | p-2y7357q195-a | {INSERT,UPDATE,DELETE,TRUNCATE} | | | row_origin + 18452 | aidb | knowledge_base_registry_source_volume | p-2y7357q195-a | {INSERT,UPDATE,DELETE,TRUNCATE} | | | row_origin +(7 rows) ``` #### Setting up background workers diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/performance_tuning.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/performance_tuning.mdx index bf6e8b3869d..7ae3768859f 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/performance_tuning.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/performance_tuning.mdx @@ -36,7 +36,7 @@ INSERT INTO test_data_10k (id, msg) SELECT generate_series(1, 10000) AS id, 'hel The optimal batch size may be very different for different models. Measure and tune the batch size for each different model you want to use. ```sql SELECT aidb.create_table_knowledge_base( - name => 'perf_test_b', + name => 'perf_test', model_name => 'dummy', -- use the model you want to optimize for source_table => 'test_data_10k', source_data_column => 'msg', diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/usage.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/usage.mdx index 673b52447aa..6f24ad02eb7 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/usage.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/knowledge_base/usage.mdx @@ -157,8 +157,8 @@ A view is available that lists all the knowledge_bases. [aidb.knowledge_bases](. ```sql SELECT * FROM aidb.knowledge_bases; __OUTPUT__ - id | name | vector_table_name | vector_table_key_column | vector_table_vector_column | model_name | topk | distance_operator | options | source_table_name | source_table_data_column | source_table_data_column_type | source_table_key_column | source_volume_name -----+---------------------+----------------------------+-------------------------+----------------------------+--------------+------+-------------------+---------+-------------------+--------------------------+-------------------------------+-------------------------+-------------------- + id | name | vector_table_name | vector_table_key_column | vector_table_vector_column | model_name | topk | distance_operator | options | source_table_name | source_table_data_column | source_table_data_column_type | source_table_key_column | source_volume_name +----+--------------------------+---------------------------------+-------------------------+----------------------------+--------------+------+-------------------+---------+-------------------+--------------------------+-------------------------------+-------------------------+-------------------- 2 | test_knowledge_base | test_knowledge_base_vector | id | embeddings | simple_model | 5 | InnerProduct | {} | test_source_table | content | Text | id | 5 | test_knowledge_base_cosa | test_knowledge_base_cosa_vector | id | embeddings | simple_model | 1 | L2 | {} | test_source_table | content | Text | id | 3 | test_knowledge_base_cos | test_knowledge_base_cos_vector | id | embeddings | simple_model | 5 | Cosine | {} | test_source_table | content | Text | id | @@ -170,8 +170,8 @@ We recommend that you select only the columns you're interested in: ```sql SELECT name, source_table_name FROM aidb.knowledge_bases; __OUTPUT__ - name | source_table_name ----------------------+------------------- + name | source_table_name +--------------------------+------------------- test_knowledge_base | test_source_table test_knowledge_base_cos | test_source_table test_knowledge_base_cosa | test_source_table diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chained_preparers.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chained_preparers.mdx index dab273a4fc8..9c1188a996b 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chained_preparers.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chained_preparers.mdx @@ -25,7 +25,7 @@ SELECT aidb.create_table_preparer( destination_table => 'chunked_data__1321', destination_data_column => 'chunk', destination_key_column => 'id', - options => '{"desired_length": 1, "max_length": 1000}'::JSONB -- Configuration for the ChunkText operation + options => '{"desired_length": 1000}'::JSONB -- Configuration for the ChunkText operation ); ``` diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text.mdx index 0c617d70705..eb503fbc5e1 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text.mdx @@ -60,18 +60,6 @@ __OUTPUT__ (9 rows) ``` -```sql --- Semantic chunking to split into the largest continuous semantic chunk that fits in the max_length -SELECT * FROM aidb.chunk_text('This sentence should be its own chunk. This too.', '{"desired_length": 1, "max_length": 1000}'); - -__OUTPUT__ - part_id | chunk ----------+---------------------------------------- - 0 | This sentence should be its own chunk. - 1 | This too. -(2 rows) -``` - ## Preparer with table data source ```sql @@ -83,7 +71,7 @@ CREATE TABLE source_table__1628 ); INSERT INTO source_table__1628 VALUES (1, 'This is a significantly longer text example that might require splitting into smaller chunks. The purpose of this function is to partition text data into segments of a specified maximum length, for example, this sentence 145 is characters. This enables processing or storage of data in manageable parts.'), - (2, 'This sentence should be its own chunk. This too.'); + (2, 'This is sentence number one. This is sentence number one.'); SELECT aidb.create_table_preparer( name => 'preparer__1628', @@ -94,7 +82,7 @@ SELECT aidb.create_table_preparer( destination_data_column => 'chunks', source_key_column => 'id', destination_key_column => 'id', - options => '{"desired_length": 1, "max_length": 1000}'::JSONB -- Configuration for the ChunkText operation + options => '{"desired_length": 120}'::JSONB -- Configuration for the ChunkText operation ); SELECT aidb.bulk_data_preparation('preparer__1628'); @@ -102,12 +90,11 @@ SELECT aidb.bulk_data_preparation('preparer__1628'); SELECT * FROM chunked_data__1628; __OUTPUT__ - id | part_id | unique_id | chunks -----+---------+-----------+--------------------------------------------------------------------------------------------------------------------------------------------------- + id | part_id | unique_id | chunks +----+---------+-----------+----------------------------------------------------------------------------------------------------------------------- 1 | 0 | 1.part.0 | This is a significantly longer text example that might require splitting into smaller chunks. - 1 | 1 | 1.part.1 | The purpose of this function is to partition text data into segments of a specified maximum length, for example, this sentence 145 is characters. - 1 | 2 | 1.part.2 | This enables processing or storage of data in manageable parts. - 2 | 0 | 2.part.0 | This sentence should be its own chunk. - 2 | 1 | 2.part.1 | This too. -(5 rows) + 1 | 1 | 1.part.1 | The purpose of this function is to partition text data into segments of a specified maximum length, for example, this + 1 | 2 | 1.part.2 | sentence 145 is characters. This enables processing or storage of data in manageable parts. + 2 | 0 | 2.part.0 | This is sentence number one. This is sentence number one. +(4 rows) ``` diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text_auto_processing.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text_auto_processing.mdx index c64bb9ef63e..c0187f12086 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text_auto_processing.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/examples/chunk_text_auto_processing.mdx @@ -29,7 +29,7 @@ SELECT aidb.create_table_preparer( destination_data_column => 'chunk', source_key_column => 'id', destination_key_column => 'id', - options => '{"desired_length": 1, "max_length": 1000}'::JSONB -- Configuration for the ChunkText operation + options => '{"desired_length": 1000}'::JSONB -- Configuration for the ChunkText operation ); SELECT aidb.set_auto_preparer('preparer__1628', 'Live'); diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/primitives.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/primitives.mdx index 62771150bbf..b1e91c8044b 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/primitives.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/primitives.mdx @@ -14,7 +14,7 @@ All data preparation operations can be customized with different options. The AP ## Chunk text -Call `aidb.chunk_text()` to break text into smaller chunks. +Call `aidb.chunk_text()` to intelligently split long text into smaller, semantically coherent chunks, ideal for processing or storage within LLM context limits. ```sql SELECT * FROM aidb.chunk_text( @@ -31,8 +31,18 @@ __OUTPUT__ (3 rows) ``` -- The `desired_length` size is the target size for the chunk. In most cases, this value also serves as the maximum size of the chunk. It's possible for a chunk to be returned that's less than the `desired` value, as adding the next piece of text may have made it larger than the `desired` capacity. -- The `max_length` size is the maximum possible chunk size that can be generated. Setting this to a value larger than `desired` means that the chunk should be as close to `desired` as possible but can be larger if it means staying at a larger semantic level. +### Options + +- `desired_length` (required): The target chunk size, in characters. This is the size the splitter will try to reach when forming each chunk, while preserving semantic structure. If `max_length` is not provided, `desired_length` also acts as the hard upper limit for the chunk size. +- `max_length` (optional): The upper bound for chunk size, in characters. If specified, the function will try to generate chunks close to `desired_length` but may extend up to `max_length` to preserve larger semantic units (like full sentences or paragraphs). Chunks will only exceed `desired_length` when it's necessary to avoid cutting across meaningful boundaries. + - Specifying `desired_length = max_length` results in fixed-size chunks (e.g., when filling a context window exactly for embeddings). + - Use a larger `max_length` if you want to stay within a soft limit but allow some flexibility to preserve higher semantic units, common in RAG, summarization, or Q&A applications. + +### Algorithm Summary + +- Text is split using a hierarchy of semantic boundaries: characters, graphemes, words, sentences, and increasingly long newline sequences (e.g., paragraphs). +- The splitter attempts to form the largest semantically valid chunk that fits within the specified size range. +- Chunks may be returned that are shorter than `desired_length` if adding the next semantic unit would exceed max_length. !!! Tip This operation transforms the shape of the data, automatically unnesting collections by introducing a `part_id` column. See the [unnesting concept](./concepts#unnesting) for more detail. diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/volume_destination.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/volume_destination.mdx index 469e34a171e..4ff9e9c119e 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/volume_destination.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/preparers/volume_destination.mdx @@ -68,7 +68,7 @@ SELECT aidb.create_volume_preparer( operation => 'ChunkText', source_volume_name => 'text_files_volume', destination_table => 'chunk_output_volume', - options => '{"desired_length": 1, "max_length": 100}'::JSONB + options => '{"desired_length": 1000}'::JSONB ); SELECT aidb.bulk_data_preparation('chunking_example_volumes'); diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/index.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/index.mdx index 0ac02c2442f..07aa60c0dfa 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/index.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/index.mdx @@ -21,8 +21,9 @@ navigation: * [aidb.create_model](models#aidbcreate_model) * [aidb.get_model](models#aidbget_model) * [aidb.delete_model](models#aidbdelete_model) -* [aidb.get_hcp_models](models#aidbget_hcp_models) +* [aidb.list_hcp_models](models#aidblist_hcp_models) * [aidb.create_hcp_model](models#aidbcreate_hcp_model) +* [aidb.sync_hcp_models](models#aidbsync_hcp_models) * [aidb.encode_text](models#aidbencode_text) * [aidb.encode_text_batch](models#aidbencode_text_batch) * [aidb.decode_text](models#aidbdecode_text) diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/models.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/models.mdx index 3a32edd9e23..14f35b44070 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/models.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/reference/models.mdx @@ -161,7 +161,7 @@ __OUTPUT__ | `delete_model` | jsonb | The name, provider, and options of the deleted model | -### `aidb.get_hcp_models` +### `aidb.list_hcp_models` Gets models running on the hybrid control plane. @@ -194,6 +194,19 @@ Creates a new model in the system by referencing a running instance in the HCP | `name` | text | | User-defined name of the model | | `hcp_model_name` | text | | Name of the model instance running on HCP | +### `aidb.sync_hcp_models` + +Creates models in the HCP and sets `is_hcp_model=true`; deletes models with that setting if not found in the HCP. + +#### Returns + +| Column | Type | Description | +| -------- | ---- | ------------------------------------------------------------------------------- | +| `status` | text | Synchronization status; either `deleted`, `unchanged`, `created`, or `skipped`. | +| `model` | text | The name the synchronized HCP model. | + + + ### `aidb.encode_text` Encodes text using a model, generating a vector representation of a given text input. diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/ai-accelerator_4.1.1_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/ai-accelerator_4.1.1_rel_notes.mdx new file mode 100644 index 00000000000..6cff0649546 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/ai-accelerator_4.1.1_rel_notes.mdx @@ -0,0 +1,38 @@ +--- +title: AI Accelerator - Pipelines 4.1.1 release notes +navTitle: Version 4.1.1 +originalFilePath: advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/src/rel_notes_4.1.1.yml +editTarget: originalFilePath +--- + +Released: 28 May 2025 + +This is a minor release that includes bug fixes. +Note: this release depends on the new PGFS version 2.0.2. If you're using PGFS together with AIDB, please update PGFS as well. + +## Highlights + +- Bug fixes and UX enhancements. + +## Enhancements + + + + + +
DescriptionAddresses
Change the tracking of "run IDs" for volume knowledge bases from a PG sequence to a PG table column

Knowledge bases with volume source need to assign an incrementing ID to each listing done on the source. +This is necessary to detect when a listing is complete and recognize which previously seen objects were not encountered any more. +In this release the method for tracking run IDs is changed to a table column since the Postgres sequence used before did not +work on Postgres Distributed (PGD) clusters.

+
Support AIDB volumes in arbitrary Postgres schemas

Volumes for AIDB can be created in arbitrary schemas in Postgres either by exlicitly passing a schema to the create function, or by +setting a "current schema" via the search path. When using volumes in AIDB pipelines, the volume reference needs to be stored. +AIDB will now store and explicitly use a schema when later executing a pipeline. Previously, the search path was used to find volumes.

+
Background worker dispatcher is no longer persistent

When background workers are enabled for AIDB, a root-worker will start a database dispatcher for each database within the Postgres instance. +This database dispatcher checks if AIDB is installed in the DB and if any pipelines need to be run in the background. +The database dispatcher is now no longer a permanent process by default. When a database does not use AIDB, the database dispatcher +exits and will be re-started to check for AIDB every 2 minutes. +This avoids holding a permanent connection to the DB that would block e.g. "drop table" commands. +If AIDB is installed in the DB, then the database dispatcher worker will keep running. Users can drop the extension in order to release the connection.

+
+ + diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/index.mdx b/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/index.mdx index a46870bd873..e8c1bb0c33e 100644 --- a/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/index.mdx +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/index.mdx @@ -4,6 +4,7 @@ navTitle: Release notes description: Release notes for EDB Postgres AI - AI Accelerator indexCards: none navigation: + - ai-accelerator_4.1.1_rel_notes - ai-accelerator_4.1.0_rel_notes - ai-accelerator_4.0.1_rel_notes - ai-accelerator_4.0.0_rel_notes @@ -23,6 +24,7 @@ The EDB Postgres AI - AI Accelerator describes the latest version of AI Accelera | AI Accelerator version | Release Date | |---|---| +| [4.1.1](./ai-accelerator_4.1.1_rel_notes) | 28 May 2025 | | [4.1.0](./ai-accelerator_4.1.0_rel_notes) | 19 May 2025 | | [4.0.1](./ai-accelerator_4.0.1_rel_notes) | 09 May 2025 | | [4.0.0](./ai-accelerator_4.0.0_rel_notes) | 05 May 2025 | diff --git a/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/src/rel_notes_4.1.1.yml b/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/src/rel_notes_4.1.1.yml new file mode 100644 index 00000000000..fa6f6cff669 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/ai-accelerator/rel_notes/src/rel_notes_4.1.1.yml @@ -0,0 +1,41 @@ +# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json +product: AI Accelerator - Pipelines +version: 4.1.1 +date: 28 May 2025 +intro: | + This is a minor release that includes bug fixes. + Note: this release depends on the new PGFS version 2.0.2. If you're using PGFS together with AIDB, please update PGFS as well. +highlights: | + - Bug fixes and UX enhancements. +relnotes: + - relnote: Change the tracking of "run IDs" for volume knowledge bases from a PG sequence to a PG table column + details: | + Knowledge bases with volume source need to assign an incrementing ID to each listing done on the source. + This is necessary to detect when a listing is complete and recognize which previously seen objects were not encountered any more. + In this release the method for tracking run IDs is changed to a table column since the Postgres sequence used before did not + work on Postgres Distributed (PGD) clusters. + jira: "AID-455" + addresses: "" + type: Enhancement + impact: High + - relnote: Support AIDB volumes in arbitrary Postgres schemas + details: | + Volumes for AIDB can be created in arbitrary schemas in Postgres either by exlicitly passing a schema to the create function, or by + setting a "current schema" via the search path. When using volumes in AIDB pipelines, the volume reference needs to be stored. + AIDB will now store and explicitly use a schema when later executing a pipeline. Previously, the search path was used to find volumes. + jira: "AID-407" + addresses: "" + type: Enhancement + impact: High + - relnote: Background worker dispatcher is no longer persistent + details: | + When background workers are enabled for AIDB, a root-worker will start a database dispatcher for each database within the Postgres instance. + This database dispatcher checks if AIDB is installed in the DB and if any pipelines need to be run in the background. + The database dispatcher is now no longer a permanent process by default. When a database does not use AIDB, the database dispatcher + exits and will be re-started to check for AIDB every 2 minutes. + This avoids holding a permanent connection to the DB that would block e.g. "drop table" commands. + If AIDB is installed in the DB, then the database dispatcher worker will keep running. Users can drop the extension in order to release the connection. + jira: "AID-459" + addresses: "" + type: Enhancement + impact: High diff --git a/advocacy_docs/pg_extensions/otel/using.mdx b/advocacy_docs/pg_extensions/otel/using.mdx index 4ca248ee123..4a61bc442f4 100644 --- a/advocacy_docs/pg_extensions/otel/using.mdx +++ b/advocacy_docs/pg_extensions/otel/using.mdx @@ -91,10 +91,10 @@ This custom query adds a count of client backends to the schedule: ## `edb_otel.pg_exporter_base_definitions` -This view contains the meter (queries and their metrics) definitions that pg_exporter brings by default. You can refresh them from the [upm-metrics-pg-exporter](https://github.com/EnterpriseDB/upm-metrics-pg-exporter/tree/main/config/collector) or the [pg_exporter collector](https://github.com/Vonng/pg_exporter/tree/main/config/collector) by running `yq` on the directory: +This view contains the meter (queries and their metrics) definitions that pg_exporter brings by default. You can refresh them from the [pg_exporter collector](https://github.com/pgsty/pg_exporter/tree/main/config) by running `yq` on the directory: ```yq -yq eval-all -o=json '. as $item ireduce ({}; . * $item)' [...]/config/collector/*.yml +yq eval-all -o=json '. as $item ireduce ({}; . * $item)' [...]/config/*.yml ``` ## Job scheduling @@ -104,7 +104,7 @@ You can use pg_cron to schedule jobs for the pg_exporter. edb_otel has auxiliary - The meter name. This is the top key in the YAML files. - A scheduling definition. This is a schedule that pg_cron will accept, -For example, the [410-pg_activity.yml](https://github.com/Vonng/pg_exporter/blob/main/config/collector/410-pg_activity.yml) query pulls output from pg_stat_activity. To run this every minute, use the cron syntax: '* * * * *'. To create the job in pg_cron: +For example, the [0410-pg_activity.yml](https://github.com/pgsty/pg_exporter/blob/main/config/0410-pg_activity.yml) query pulls output from pg_stat_activity. To run this every minute, use the cron syntax: '* * * * *'. To create the job in pg_cron: ```sql SELECT edb_otel.schedule_from_pg_exporter_definition(meters->'pg_activity', '* * * * *') diff --git a/advocacy_docs/playground/1/01_examples/code-blocks.mdx b/advocacy_docs/playground/1/01_examples/code-blocks.mdx index 4ba74dcf2a0..cd492c9f1ef 100644 --- a/advocacy_docs/playground/1/01_examples/code-blocks.mdx +++ b/advocacy_docs/playground/1/01_examples/code-blocks.mdx @@ -33,3 +33,13 @@ asdasd asdasd asdasdafasfa + +```sql +SELECT * FROM aidb.retrieve_text('test_knowledge_base', 'jacket', 2); +__OUTPUT__ + key | value | distance +-------+----------------------------------------------------+-------------------- + 19337 | United Colors of Benetton Men Stripes Black Jacket | 0.2994317672742334 + 55018 | Lakme 3 in 1 Orchid Aqua Shine Lip Color | 0.3804609668507203 +(2 rows) +``` diff --git a/install_template/config.yaml b/install_template/config.yaml index 717a2de011e..a73ff98b9a1 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -67,49 +67,49 @@ products: platforms: - name: RHEL 8 arch: ppc64le - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: RHEL 9 arch: ppc64le - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: RHEL 9 or OL 9 arch: arm64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: Debian 11 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: Debian 12 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: Debian 12 arch: arm64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: Ubuntu 24.04 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: SLES 15 arch: x86_64 - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: SLES 15 arch: ppc64le - supported versions: [42.7.3.2] + supported versions: [42.7.3.3] - name: Migration Toolkit platforms: - name: RHEL 8 or OL 8 diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-9-or-ol-9.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-9-or-ol-9.njk index cb16658a1ef..3d69956043c 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/rhel-9-or-ol-9.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/rhel-9-or-ol-9.njk @@ -4,7 +4,7 @@ {{ super() }} - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/efm/5/efm_rel_notes/index.mdx b/product_docs/docs/efm/5/efm_rel_notes/index.mdx index d94f53c7105..b26a0706525 100644 --- a/product_docs/docs/efm/5/efm_rel_notes/index.mdx +++ b/product_docs/docs/efm/5/efm_rel_notes/index.mdx @@ -1,8 +1,7 @@ --- title: "Release notes" --- -The Failover Manager documentation describes the latest version of Failover Manager. These release notes -cover what was new in each release. +The Failover Manager documentation describes the latest version of Failover Manager. These release notes cover what was new in each release. The standard support end date for each release is 18 months after the next release. | Version | Release Date | | ------- | ------------ | diff --git a/product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx index 1e9148f8014..fb5ffdd0c4e 100644 --- a/product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx index 7dea12d601b..45b5b6812fb 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx @@ -45,7 +45,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx index be24d314ac7..395c538b63f 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx index 3c5afba3625..e5e5491ca90 100644 --- a/product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx index ae60d9d5c9a..def9099b539 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx @@ -45,7 +45,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx index 5fbb6530350..2d94fb8c6c9 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx index ebc2c34f02b..2451ad5f6d1 100644 --- a/product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx index 80120558b8e..535ed9e16ae 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx @@ -45,7 +45,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx index 9a03064dbb7..d4aeb7c82ee 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx index 2032c8d89c3..90d008b54f2 100644 --- a/product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_9.mdx index 341208734f0..050d57fc7ec 100644 --- a/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_9.mdx @@ -45,7 +45,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_9.mdx index 961ab27aee0..f1bf996c9ef 100644 --- a/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx index 7d59dd766fa..846fa4203e9 100644 --- a/product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx index d10c4b8ae7f..8f7702b2bd6 100644 --- a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx @@ -45,7 +45,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx index 2e6976251d7..daf4c37ac0e 100644 --- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx @@ -43,7 +43,7 @@ Before you begin the installation process: - If you are also installing PostGIS, enable additional repositories to resolve dependencies: ```shell - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ARCH=$( /bin/arch ); subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` !!!note diff --git a/product_docs/docs/epas/17/reference/sql_reference/02_data_types/01_numeric_types.mdx b/product_docs/docs/epas/17/reference/sql_reference/02_data_types/01_numeric_types.mdx index 2bdd2fbde95..12fccda758d 100644 --- a/product_docs/docs/epas/17/reference/sql_reference/02_data_types/01_numeric_types.mdx +++ b/product_docs/docs/epas/17/reference/sql_reference/02_data_types/01_numeric_types.mdx @@ -68,7 +68,7 @@ If the precision or scale of a value is greater than the declared precision or s Numeric values are physically stored without any extra leading or trailing zeroes. Thus, the declared precision and scale of a column are maximums, not fixed allocations. (In this sense the `NUMBER` type is more akin to `VARCHAR(N)` than to `CHAR(N)`.) The actual storage requirement is two bytes for each group of four decimal digits, plus three to eight bytes overhead. -In addition to ordinary numeric values, the `NUMBER` type allows the special value NaN, meaning “not-a-number”. Any operation on NaN yields another NaN. When writing this value as a constant in an SQL command, you must put quotes around it, for example U`PDATE table SET x = 'NaN'`. On input, the string `NaN` is recognized in a case-insensitive manner. +In addition to ordinary numeric values, the `NUMBER` type allows the special value NaN, meaning “not-a-number”. Any operation on NaN yields another NaN. When writing this value as a constant in an SQL command, you must put quotes around it, for example `UPDATE table SET x = 'NaN'`. On input, the string `NaN` is recognized in a case-insensitive manner. !!!Note In most implementations of the “not-a-number” concept, `NaN` is not considered equal to any other numeric value (including `NaN`). In order to allow numeric values to be sorted and used in tree-based indexes, PostgreS treats `NaN` values as equal, and greater than all non-`NaN` values. @@ -164,4 +164,4 @@ To insert the next value of the sequence into the serial column, specify that th The type names `SERIAL` and `SERIAL4` are equivalent: both create integer columns. The type names `BIGSERIAL` and `SERIAL8` work the same way, except that they create a bigint column. `BIGSERIAL` should be used if you anticipate the use of more than 2147483648 identifiers (2 to the 31st power)over the lifetime of the table. The type names `SMALLSERIAL` and `SERIAL2` also work the same way, except that they create a `SMALLINT` column. -The sequence created for a `SERIAL` column is automatically dropped when the owning column is dropped. You can drop the sequence without dropping the column, but this will force removal of the column default expression. \ No newline at end of file +The sequence created for a `SERIAL` column is automatically dropped when the owning column is dropped. You can drop the sequence without dropping the column, but this will force removal of the column default expression. diff --git a/product_docs/docs/hadoop_data_adapter/2/10c_example_order_by_pushdown.mdx b/product_docs/docs/hadoop_data_adapter/2/10c_example_order_by_pushdown.mdx index 8f5e6fbb859..ce54db3370e 100644 --- a/product_docs/docs/hadoop_data_adapter/2/10c_example_order_by_pushdown.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/10c_example_order_by_pushdown.mdx @@ -69,7 +69,9 @@ __OUTPUT__ --------------------- Foreign Scan on emp (1 row) +``` +```sql edb=# SET hdfs_fdw.enable_order_by_pushdown TO OFF; SET edb=# EXPLAIN (COSTS OFF) SELECT * FROM emp order by deptno; diff --git a/product_docs/docs/pem/10/installing/linux_arm64/pem_debian_12.mdx b/product_docs/docs/pem/10/installing/linux_arm64/pem_debian_12.mdx index 7786d3a2e01..8572f1037c1 100644 --- a/product_docs/docs/pem/10/installing/linux_arm64/pem_debian_12.mdx +++ b/product_docs/docs/pem/10/installing/linux_arm64/pem_debian_12.mdx @@ -84,7 +84,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_arm64/pem_rhel_9.mdx b/product_docs/docs/pem/10/installing/linux_arm64/pem_rhel_9.mdx index c90be7fd409..e924391056c 100644 --- a/product_docs/docs/pem/10/installing/linux_arm64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/10/installing/linux_arm64/pem_rhel_9.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_8.mdx index 908bc35a733..35e0a929a95 100644 --- a/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_8.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_9.mdx index 3a2b5903759..7960135b99a 100644 --- a/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/10/installing/linux_ppc64le/pem_rhel_9.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/10/installing/linux_ppc64le/pem_sles_15.mdx index 4c864b50158..6c3a9454a2a 100644 --- a/product_docs/docs/pem/10/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/10/installing/linux_ppc64le/pem_sles_15.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_11.mdx index 7cae95ee1b7..df56e188837 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_11.mdx @@ -98,7 +98,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_12.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_12.mdx index be3c3962405..4964d6d5341 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_12.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_debian_12.mdx @@ -84,7 +84,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_8.mdx index dbe1f0d0d9e..4095299a72e 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_8.mdx @@ -91,7 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_9.mdx index 8f36d227312..1a5ddd39d84 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_other_linux_9.mdx @@ -91,7 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_8.mdx index 6caa5014e31..5a98897f891 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_8.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_9.mdx index c2a6ae0487f..7a884436c26 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_rhel_9.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_sles_15.mdx index 347edcbd792..3b06c91e6fe 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_sles_15.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_22.mdx index de43700e8ef..2518ac21ae4 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -98,7 +98,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_24.mdx b/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_24.mdx index 376b0b286a7..03e030ebba5 100644 --- a/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_24.mdx +++ b/product_docs/docs/pem/10/installing/linux_x86_64/pem_ubuntu_24.mdx @@ -98,7 +98,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/10/monitoring_failover_manager.mdx b/product_docs/docs/pem/10/monitoring_failover_manager.mdx index 82a9bd7ddad..291144ac61f 100644 --- a/product_docs/docs/pem/10/monitoring_failover_manager.mdx +++ b/product_docs/docs/pem/10/monitoring_failover_manager.mdx @@ -15,7 +15,7 @@ To monitor the status of a Failover Manager cluster on the Streaming Replication - Use the **EFM Cluster Name** field to specify the name of the Failover Manager cluster. The cluster name is the prefix of the name of the cluster properties file. For example, if your cluster properties file is named `efm.properties`, your cluster name is efm. -- Use the **EFM Installation Path** field to specify the location of the Failover Manager binary file. By default, the Failover Manager binary file is installed in `/usr/efm-/bin`, where `` is the EFM version. +- Use the **EFM Installation Path** field to specify the location of the Failover Manager binary file. By default, the Failover Manager binary file is installed in `/usr/edb/efm-/bin`, where `` is the EFM version. !!! Note To monitor Failover Manager, the PEM agent executes the `efm cluster-status-json ` command as the user efm. This command fails if the cluster properties file isn't in the efm user's home directory. diff --git a/product_docs/docs/pem/10/registering_agent.mdx b/product_docs/docs/pem/10/registering_agent.mdx index 7bdcae3656c..7273755aa8d 100644 --- a/product_docs/docs/pem/10/registering_agent.mdx +++ b/product_docs/docs/pem/10/registering_agent.mdx @@ -26,7 +26,8 @@ If you don't want the installer to register the agent, clear the **Register now* ## Registering a PEM agent using the pemworker utility The pemworker utility is installed automatically with the PEM agent. It's located in the `/usr/edb/pem/agent/bin` directory on Linux and `C:\Program Files\edb\pem\agent-x64\bin` on Windows. -To register an agent, set the PEM server password, invoke the utility as shown in the examples, and add the relevant options from the table as needed. Follow each option with a corresponding value. + +To register an agent, set the PEM server database user password, invoke the utility as shown in the examples, and add the relevant options from the table as needed. Follow each option with a corresponding value. #### Linux @@ -48,7 +49,7 @@ set PEM_SERVER_PASSWORD=edb |---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `--pem-server` | The IP address of the PEM backend database server. This parameter is required. | | `--pem-port` | The port of the PEM backend database server. The default value is `5432`. | -| `--pem-user` | The name of a database with the `pem_admin` role and the `rolcreaterole` flag set (or a superuser) on the PEM backend database server. This user will be used to connect to the PEM server to perform agent registration. This parameter is required. | +| `--pem-user` | The name of a database user with the `pem_admin` role and the `rolcreaterole` flag set on the PEM backend database server, or a superuser. This user will be used to connect to the PEM server to perform agent registration. This parameter is required. | | `--pem-agent-user` | The name of a database user on the PEM server backend database server. After registration, the agent will use this user to open connections to the PEM database server to write probe data, evaluate alerts, etc. This parameter is optional. If omitted, the agent will connect using a new user created during registration named `agent` where `` is the agent ID. Note that this user is always created and even if you specify a `pem-agent-user` the agent will use `SET ROLE agent` to switch roles after the connection is made. | | `--pem-ssl-mode` | The [SSL mode](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION) to be used by the PEM agent user (see above). The possible values are `prefer`, `require`, `disable`, `verify-CA`, and `verify-full`. The default value is `require`. | | `--cert-path` | The complete path to a directory in which certificates will be stored. If you don't provide a path, certificates are created in `~/.pem` on Linux and `%APPDATA%/pem` on Windows. | diff --git a/product_docs/docs/pem/9/installing/linux_arm64/pem_debian_12.mdx b/product_docs/docs/pem/9/installing/linux_arm64/pem_debian_12.mdx index b6b73bf44c6..5f02c1a7c4b 100644 --- a/product_docs/docs/pem/9/installing/linux_arm64/pem_debian_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_arm64/pem_debian_12.mdx @@ -84,7 +84,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx index 68baff4cd0c..dd2e7784d0f 100644 --- a/product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx index 41d8ad0174f..46eaea1e478 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx index 3bc1bf50730..5cf84b1cb92 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx index 6d6e943290c..f077242c5da 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx index 35371eec6a4..0e21836daa8 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx @@ -98,7 +98,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_12.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_12.mdx index e7eeb67694e..a5b99c5272e 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_12.mdx @@ -84,7 +84,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx index f6e9d3c9392..0625fc86833 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx @@ -91,7 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx index 256adf75a2a..8da0f13799c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx @@ -91,7 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx index 6298f320483..531977d30f6 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx index a8148e3eb45..e406dc5c60c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx index be09aa91646..405a3e0d40c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx @@ -90,7 +90,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx index fff61fab1c3..b00aa90d698 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -98,7 +98,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx index 0f2aa4d6eb9..928e90b1f9b 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -98,7 +98,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - - The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory. ## Supported locales diff --git a/product_docs/docs/pem/9/registering_agent.mdx b/product_docs/docs/pem/9/registering_agent.mdx index 5c76d6bb385..a9beba53b94 100644 --- a/product_docs/docs/pem/9/registering_agent.mdx +++ b/product_docs/docs/pem/9/registering_agent.mdx @@ -28,7 +28,7 @@ If you don't want the installer to register the agent, clear the **Register now* The pemworker utility is installed with the PEM agent. It's located in `/usr/edb/pem/agent/bin` on Linux and `C:\Program Files\edb\pem\agent-x64\bin` on Windows. -To register an agent, set the PEM server password, invoke the utility as shown in the examples, and add the relevant options from the table as needed. Follow each option with a corresponding value. +To register an agent, set the PEM server database user password, invoke the utility as shown in the examples, and add the relevant options from the table as needed. Follow each option with a corresponding value. #### Linux diff --git a/product_docs/docs/pgd/4/cli/command_ref/index.mdx b/product_docs/docs/pgd/4/cli/command_ref/index.mdx index d0968c906fe..c3485d4ca74 100644 --- a/product_docs/docs/pgd/4/cli/command_ref/index.mdx +++ b/product_docs/docs/pgd/4/cli/command_ref/index.mdx @@ -25,10 +25,10 @@ You can use it to inspect and manage cluster resources. ## See also - [check-health](pgd_check-health) - [show-camo](pgd_show-camo) -- [show-clockscrew](pgd_show-clockskew) +- [show-clockskew](pgd_show-clockskew) - [show-events](pgd_show-events) - [show-nodes](pgd_show-nodes) - [show-raft](pgd_show-raft) - [show-replslots](pgd_show-replslots) - [show-subscriptions](pgd_show-subscriptions) -- [show-version](pgd_show-version) \ No newline at end of file +- [show-version](pgd_show-version) diff --git a/product_docs/docs/pgd/5.7/index.mdx b/product_docs/docs/pgd/5.7/index.mdx index fbd5e26d9e6..87b5f673f07 100644 --- a/product_docs/docs/pgd/5.7/index.mdx +++ b/product_docs/docs/pgd/5.7/index.mdx @@ -55,6 +55,7 @@ categories: pdf: true directoryDefaults: version: "5.7.0" +displayBanner: 'Warning: You are not reading the most recent version of this documentation.
Documentation improvements are made only to the latest version.
As per semantic versioning, PGD minor releases remain backward compatible and may include important bug fixes and enhancements.
We recommend upgrading the latest minor release as soon as possible.
If you want up-to-date information, read the latest PGD documentation.' --- diff --git a/product_docs/docs/pgd/5.7/quickstart/quick_start_aws.mdx b/product_docs/docs/pgd/5.7/quickstart/quick_start_aws.mdx index df28a4ee2b6..2afe7714d78 100644 --- a/product_docs/docs/pgd/5.7/quickstart/quick_start_aws.mdx +++ b/product_docs/docs/pgd/5.7/quickstart/quick_start_aws.mdx @@ -275,7 +275,8 @@ Connections Ok All BDR nodes are accessible Raft Ok Raft Consensus is working correctly Replication Slots Ok All PGD replication slots are working correctly Clock Skew Ok Clock drift is within permissible limit -Versions Ok All nodes are running the same PGD version``` +Versions Ok All nodes are running the same PGD version +``` Or, you can use `pgd nodes list` to ask PGD to show you the data-bearing nodes in the cluster: diff --git a/product_docs/docs/pgd/5.8/quickstart/quick_start_aws.mdx b/product_docs/docs/pgd/5.8/quickstart/quick_start_aws.mdx index df28a4ee2b6..2afe7714d78 100644 --- a/product_docs/docs/pgd/5.8/quickstart/quick_start_aws.mdx +++ b/product_docs/docs/pgd/5.8/quickstart/quick_start_aws.mdx @@ -275,7 +275,8 @@ Connections Ok All BDR nodes are accessible Raft Ok Raft Consensus is working correctly Replication Slots Ok All PGD replication slots are working correctly Clock Skew Ok Clock drift is within permissible limit -Versions Ok All nodes are running the same PGD version``` +Versions Ok All nodes are running the same PGD version +``` Or, you can use `pgd nodes list` to ask PGD to show you the data-bearing nodes in the cluster: diff --git a/src/components/card-decks.js b/src/components/card-decks.js index 2042055eaa3..28a7535ce90 100644 --- a/src/components/card-decks.js +++ b/src/components/card-decks.js @@ -27,16 +27,24 @@ const FullCard = ({ card }) => {

{card.description}

- {card.items.map((child) => ( - - {child.navTitle || child.title} - {child.interactive && } - - ))} + {card.items.slice(0, 5).map( + (child, i) => + (i === 4 && card.items.length > 5 && ( + + {`+ ${card.items.length - 4} more`} + + )) || + ((i < 5 || (i === 4 && card.items.length <= 4)) && ( + + {child.navTitle || child.title} + {child.interactive && } + + )), + )}
@@ -54,16 +62,24 @@ const ExtraCard = ({ card }) => {

{card.description}

- {card.items.map((child) => ( - - {child.navTitle || child.title} - {child.interactive && } - - ))} + {card.items.slice(0, 5).map( + (child, i) => + (i === 4 && card.items.length > 5 && ( + + {`+ ${card.items.length - 4} more`} + + )) || + ((i < 5 || (i === 4 && card.items.length <= 4)) && ( + + {child.navTitle || child.title} + {child.interactive && } + + )), + )}
diff --git a/src/components/code-block.js b/src/components/code-block.js index 0a901c982bb..81100638ad6 100644 --- a/src/components/code-block.js +++ b/src/components/code-block.js @@ -2,6 +2,7 @@ import React, { useState } from "react"; import { Button } from "react-bootstrap"; import { Tooltip } from "react-bootstrap"; import { OverlayTrigger } from "react-bootstrap"; +import { useLocation } from "@gatsbyjs/reach-router"; const childToString = (child) => { if (typeof child === "string") { @@ -22,12 +23,13 @@ const popExtraNewLines = (code) => { } }; -const splitChildrenIntoCodeAndOutput = (rawChildren) => { +const splitChildrenIntoCodeAndOutput = (rawChildren, urlpath) => { if (!rawChildren) { return [[], []]; } - const splitRegex = /(?:\s+|^)__OUTPUT__\s*(?:\n+|$)/; + // Simplified regex to split on the __OUTPUT__ marker + const splitRegex = /(?:\n|^)[ \t\f\v]*__OUTPUT__[ \t\f\v]*(?:\n|$)/; const code = []; const output = []; @@ -40,6 +42,12 @@ const splitChildrenIntoCodeAndOutput = (rawChildren) => { if (splitFound) { // we've already split, toss it into output and move on output.push(childToString(child)); + // warn if we do find another __OUTPUT__ marker - this is likely a mistake + if (splitRegex.test(output.at(-1))) + console.warn( + urlpath + + ": Found another __OUTPUT__ marker after the first one, this is likely a mistake.", + ); continue; } @@ -151,10 +159,11 @@ const OutputPre = ({ content }) => ( ); const CodeBlock = ({ children, codeLanguages, ...otherProps }) => { + const location = useLocation(); const childIsComponent = !!children.props; // true in normal usage, false if raw 
 tags are used
 
   const [codeContent, outputContent] = childIsComponent
-    ? splitChildrenIntoCodeAndOutput(children.props.children)
+    ? splitChildrenIntoCodeAndOutput(children.props.children, location.pathname)
     : [children, ""];
 
   const startWrapped = false;