Fix pg_dump command syntax for database backup

[tonytrinh19]

Summary by CodeRabbit

• Documentation
  • Updated the backup/dump command documentation to include an explicit database selector flag, ensuring clearer database targeting and improved command accuracy.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A documentation update to the PostgreSQL command cheat sheet that adds the -d <database_name> flag to the pg_dump command, providing explicit database targeting for backup operations.

Changes

Cohort / File(s)	Summary
Documentation Update docs/installation-steps-advanced/MaintainCommandsCheatSheet.md	Modified pg_dump command in "Backup / Dump the data" step to include -d <database_name> flag for explicit database selection

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A flag so small, but oh so wise,
pg_dump now clearly specifies!
Which database to backup today,
No ambiguity gets in the way! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: fixing the pg_dump command syntax in the database backup documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}