Date: Mon, 26 Jan 2026 19:24:45 +0000 (UTC)
From: felix.quintgz@yahoo.com
To: pgsql-general@lists.postgresql.org
Message-ID: <1244937982.4358855.1769455485523@mail.yahoo.com>
In-Reply-To: <32C440DF-84C3-48D3-AF25-C0D977359F56@thebuild.com>
References: <1730736265.4259921.1769443263077.ref@mail.yahoo.com> <1730736265.4259921.1769443263077@mail.yahoo.com> <f88a803f-2954-44c5-bd29-e7f1dc5f9d02@aklaver.com> <CANzqJaAygQG3F3fKe25YV765kUkO=UQqefACpo+2KQJXew7g-Q@mail.gmail.com> <868938296.4311067.1769449951678@mail.yahoo.com> <CANzqJaBnBBAWO7ot2V+oSNpR7VSnkAELMX0aqZcP=rHs2ddoig@mail.gmail.com> <2022327491.4341234.1769452625380@mail.yahoo.com> <32C440DF-84C3-48D3-AF25-C0D977359F56@thebuild.com>
Subject: Re: About backups
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Length: 1064
Archived-At: <https://www.postgresql.org/message-id/1244937982.4358855.1769455485523%40mail.yahoo.com>
Precedence: bulk

A full database backup is the requirement. A database restore is optional, =
but that's negotiable; the backup is not.=20
All of this must be done without access to the server or the database itsel=
f, solely through the application, and the user must have the necessary per=
missions 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 back=
up.

 On Monday, January 26, 2026 at 01:42:55 PM GMT-5, Christophe Pettus <xof@t=
hebuild.com> wrote:
> On Jan 26, 2026, at 10:37, felix.quintgz@yahoo.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?=C2=A0 I assume it's not "the d=
atabase can be backed up completely by issuing an SQL command."=C2=A0 If we=
 know what the precise requirement is, we might be able to provide more spe=
cific guidance.