We noticed that the repository doesn't have a switch to manage the extensions for end users. We would like to propose the addition of a feature that allows users to easily manage unnecessary extensions and tools while keeping them enabled by default.
Proposal:
Currently, managing unnecessary extensions and tools can be challenging for end users. We suggest implementing a feature that introduces switches or flags for these extensions and tools, making it user-friendly to enable/disable them as needed. This will provide flexibility while ensuring that all extensions and tools are initially enabled.
The following extensions and tools would be good candidates for switches:
extra_window_functions
first_last_agg
hll
pgq_node
postgis
timescaled
We might include more.
Benefits:
Improved user experience for managing extensions and tools.
Greater flexibility in customizing PostgreSQL installations.
All extensions and tools remain enabled by default, ensuring no disruption to existing deployments.
Are you open to receiving a Pull Request for this proposal? We would be willing to contribute to the implementation if the community is interested in pursuing this enhancement.
Issue Summary:
We noticed that the repository doesn't have a switch to manage the extensions for end users. We would like to propose the addition of a feature that allows users to easily manage unnecessary extensions and tools while keeping them enabled by default.
Proposal:
Currently, managing unnecessary extensions and tools can be challenging for end users. We suggest implementing a feature that introduces switches or flags for these extensions and tools, making it user-friendly to enable/disable them as needed. This will provide flexibility while ensuring that all extensions and tools are initially enabled.
The following extensions and tools would be good candidates for switches:
We might include more.
Benefits:
Are you open to receiving a Pull Request for this proposal? We would be willing to contribute to the implementation if the community is interested in pursuing this enhancement.
cc: @brokenpip3, @JohnMoyaC