pgadmin-org / pgadmin-org/pgadmin4

Restore item in server or Databases menu (RM #4832)

Open
#3,060 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature
Dominant language
Python
Stars
3.8k
Forks
891
Avg merge
4d 7h
Merged PRs (30d)
8

Description

Issue migrated from Redmine: https://redmine.postgresql.org/issues/4832
Originally created by A. Kromic at 2019-10-14 07:19:45 UTC.

A pgAdmin4 feature I have always wanted is having some "restore" command in the server or Databases context menu. That would make restoring databases much easier, especially during development and testing when various changes occur frequently.

Currently there are two options for restoring databases in pgAdmin from custom format backups, both a bit inconvenient:

Manually create database with the required name, then use Restore from its context menu; this has more steps than needed - there is no need to create the database manually

Use Restore from any existing database's menu, enabling the "CREATE DATABASE" option; faster, but potentially dangerous or inconvenient if one manages to overwrite the other database by mistake

For someone frequently dumping and restoring various databases from within pgAdmin4 while also doing development in it, the new menu item would be quite useful. Alternatively, it could be added as an option in the Create / Database menu; something like "Create Database from backup".

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing Restore action on a database and the Create/Database flow, then compare whether a server or Databases context-menu entry is the better starting point. Done means a user can restore a custom-format backup without manually creating the target database, while avoiding accidental overwrites.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, python
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.