Summary
Confusing/inconsistent instructions for configuring extensions that must be added to shared_preload_libraries.
Where did you see the problem?
https://github.com/EnterpriseDB/docs/blob/7107a3457167c0f75a9b081bb373c9144e30978e/product_docs/docs/tpa/23/reference/postgresql.conf.mdx
Expected behavior
This page says that extensions that need shared_preload_library entires and that are recognised by TPA as such should be added to postgres_extensions. This contradicts the other documentation (in https://github.com/EnterpriseDB/tpa-internal/blob/main/docs/src/postgres_extension_configuration.md) that says you need to add them to extra_postgres_extensions.
Additionally, the list of extensions recognised by TPA is not provided in the online docs, which is inconvenient -- the user needs to know that the other document exist and look it up for the list of extensions. They need to be included in the online page as well.
Screenshots
No response
Browser / Platform
No response
Additional notes
No response
Summary
Confusing/inconsistent instructions for configuring extensions that must be added to
shared_preload_libraries.Where did you see the problem?
https://github.com/EnterpriseDB/docs/blob/7107a3457167c0f75a9b081bb373c9144e30978e/product_docs/docs/tpa/23/reference/postgresql.conf.mdx
Expected behavior
This page says that extensions that need
shared_preload_libraryentires and that are recognised by TPA as such should be added topostgres_extensions. This contradicts the other documentation (inhttps://github.com/EnterpriseDB/tpa-internal/blob/main/docs/src/postgres_extension_configuration.md) that says you need to add them toextra_postgres_extensions.Additionally, the list of extensions recognised by TPA is not provided in the online docs, which is inconvenient -- the user needs to know that the other document exist and look it up for the list of extensions. They need to be included in the online page as well.
Screenshots
No response
Browser / Platform
No response
Additional notes
No response