Hello pgweb team !

pgweb's query history is currently in memory and ephemeral, meaning it is lost every time the server restarts. In environments like Kubernetes, where server instances are often transient, this results in a loss of valuable user context and repeated effort for common queries.

a Proposed Solution:
Implement an optional feature to enable the persistence of query history. This will allow users to retain their pgweb query history across server restarts, ensuring continuity and
improving the user experience, especially in dynamic or ephemeral deployment scenarios.

Key Aspects:

• Opt-in Functionality: it would be great to have the choice to enable or disable this feature via a clear configuration setting (e.g., a command-line flag or an environment variable).
• Configurable Storage: Provide an option to specify where the persistent history data will be stored. This should support a local file-based approach, allowing the history to reside
  alongside the pgweb instance.
• Resilience: The persistent history should be robust enough to survive server shutdowns, restarts, and redeployments in containerized environments.

Benefits:

• Improved User Experience: Users will no longer lose their query history, making pgweb more convenient and efficient for regular use.
• Enhanced Productivity: The ability to access past queries without retyping them saves time and reduces errors.
• Cloud-Native Compatibility: This feature addresses a critical need for pgweb deployments in ephemeral infrastructure, making it more suitable for modern cloud environments.

Thanks for you help,
Regards

Helldrum