Re: About backups

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.

The postgresql-client option is probably the right one.
I still have the restore history part to do, but the main thing is the backup.

On Monday, January 26, 2026 at 01:42:55 PM GMT-5, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
> On Jan 26, 2026, at 10:37, felix(dot)quintgz(at)yahoo(dot)com wrote:
>
> I can't change my expectations. It's either you do it or I won't certify you, and you won't be able to use the application.
> That's how a certification body works, and there's nothing I can do about it.

Can you articulate the specific requirement?  I assume it's not "the database can be backed up completely by issuing an SQL command."  If we know what the precise requirement is, we might be able to provide more specific guidance.