Re: About backups - Mailing list pgsql-general

From felix.quintgz@yahoo.com
Subject Re: About backups
Date
Msg-id 532797406.4381326.1769458572799@mail.yahoo.com
Whole thread Raw
In response to Re: About backups  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Thank you all so much.
With what they've given me, I can continue in my job.

 On Monday, January 26, 2026 at 03:02:45 PM GMT-5, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
 On 1/26/26 11:24, felix.quintgz@yahoo.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
usermust have the necessary permissions within the application. 
 > > The postgresql-client option is probably the right one.

FYI, in Postgres 17+ you have in the client program pg_basebackup the
option to do incremental backups.

In addition there are third party tools that offer more options for backups:

https://pgbarman.org/

https://pgbackrest.org/

> 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@thebuild.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?  I assume it's not "the database can be backed up completely by issuing
anSQL command."  If we know what the precise requirement is, we might be able to provide more specific guidance. 
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: About backups
Next
From: Christophe Pettus
Date:
Subject: AioIoCompletion with io_worker = sync?