GH-446: [Storage] Container baked with Tabular Data in Postgres

[vibhatha]

This PR includes the following.

1. Postgres Database image with data backed in at the build stage.
2. minor version changes to database backup version used in the restoration process.

Generated By: Claude and Antigravity

This PR closes #446.

[gemini-code-assist]

Summary of Changes

Hello @vibhatha, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a robust mechanism for creating a PostgreSQL Docker image that comes pre-loaded with tabular data, specifically tailored for deployment on the Choreo platform. It enhances the development workflow by providing a ready-to-use database instance with relevant data baked in, while also addressing environmental challenges such as read-only filesystems. The changes include an upgrade to the latest PostgreSQL version and updated guidance for deployment.

Highlights

• PostgreSQL Image with Baked-in Data: The PostgreSQL Docker image now includes pre-populated tabular data directly at the build stage, streamlining database setup for development environments.
• PostgreSQL Version Upgrade: The base PostgreSQL image has been updated from version 16 to version 17, bringing the latest features and improvements.
• Choreo Platform Compatibility: A new startup script and configuration changes address the read-only filesystem constraints of platforms like Choreo, allowing the baked-in data to be copied to a writable location at runtime.
• Backup Version Update: The version of the database backup used for restoration during the build process has been updated to 0.0.3.
• Deployment Documentation: New documentation has been added to guide users on configuring necessary volume mounts for self-hosted databases (Postgres and Neo4j) when deploying to Choreo.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the PostgreSQL Docker image to bake in data at build time, which is a good approach for creating self-contained development or testing environments. The changes are well-structured, including updates to the Dockerfile, a new startup script to handle read-only filesystems, and corresponding documentation.

My review focuses on improving security and maintainability. I've identified a critical issue with a hardcoded password, a high-severity issue with an overly permissive database access configuration, and a medium-severity suggestion to improve the Dockerfile's readability by extracting a large script. Addressing these points will make the container more secure and easier to maintain.

[ChanukaUOJ]

Added some comments