add clean postgres dump for safer restores

[KavindaRajapaksha]

Fix the creating a dump of a Postgres db does not delete existing table.
@vibhatha @zaeema-n check them and need any changes let me know
Issue:#319

[gemini-code-assist]

Summary of Changes

Hello, 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 enhances the robustness of PostgreSQL database backups by modifying the pg_dump command to ensure a clean and idempotent restore process. The change prevents issues where existing tables might cause conflicts during restoration, thereby improving the overall reliability of the development environment's data management.

Highlights

• PostgreSQL Backup Command Update: The pg_dump command used for PostgreSQL backups in init.sh has been updated to include the --clean and --if-exists flags. This ensures that when a backup is restored, existing tables are dropped before recreation, preventing conflicts and making the restore process idempotent.
• Documentation Update: The backup_and_restore_workflow.md documentation has been updated to reflect the change in PostgreSQL backup behavior, explicitly stating that backups are now created with clean drops, making restores safe and idempotent.

Changelog

• deployment/development/backup_and_restore_workflow.md
  • Added a note explaining that PostgreSQL backups now use --clean --if-exists for safe and idempotent restores.
• deployment/development/init.sh
  • Modified the pg_dump command to include --clean --if-exists flags for safer database backups.

Activity

• No human activity has been recorded on this pull request yet.

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 improves the PostgreSQL backup process by adding the --clean and --if-exists flags to pg_dump. This makes database restores safer and idempotent, which is a valuable enhancement. The accompanying documentation update in backup_and_restore_workflow.md is clear and accurately reflects the change. I have one suggestion for init.sh to improve maintainability by using the configured environment variable for the PostgreSQL user instead of a hardcoded value.

[Copilot]

Pull request overview

Updates the development backup/restore workflow to make PostgreSQL restores more repeatable by embedding cleanup statements into the generated SQL dump.

Changes:

• Add pg_dump --clean --if-exists to the PostgreSQL backup command.
• Document the intended “repeatable restore” behavior in the dev backup/restore workflow guide.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
deployment/development/init.sh	Adds --clean --if-exists to the pg_dump invocation used for dev PostgreSQL backups.
deployment/development/backup_and_restore_workflow.md	Documents the new PostgreSQL dump behavior and its intended restore implications.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[zaeema-n]

Thank you for this PR @KavindaRajapaksha. Please also address any of the bot comments that were left.

This PR closes #319

[KavindaRajapaksha]

@zaeema-n added the corrections asked by bot