| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | felix(dot)quintgz(at)yahoo(dot)com |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: About backups |
| Date: | 2026-01-26 20:11:22 |
| Message-ID: | 8C907CFF-EF9A-4BD8-A9B9-47DCC8D1A65E@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Jan 26, 2026, at 11:24, felix(dot)quintgz(at)yahoo(dot)com wrote:
>
> A full database backup is the requirement. A database restore is optional, but that's negotiable; the backup is not.
> All of this must be done without access to the server or the database itself, solely through the application, and the user must have the necessary permissions within the application.
In that case, running pg_dump on the application server is probably the way to go. pg_dump can produce a single file that can be used to do a full restore, and it's smaller than an equivalent bindary backup (since it includes index definitions, but not the contents of the index itself). Of course, if it's a 100GB database, you'll end up with a huge file no matter what, but nothing to do about that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | felix.quintgz | 2026-01-26 20:16:12 | Re: About backups |
| Previous Message | Adrian Klaver | 2026-01-26 20:02:23 | Re: About backups |