Date: Mon, 26 Jan 2026 18:37:05 +0000 (UTC)
From: felix.quintgz@yahoo.com
To: pgsql-general@lists.postgresql.org
Message-ID: <2022327491.4341234.1769452625380@mail.yahoo.com>
In-Reply-To: <CANzqJaBnBBAWO7ot2V+oSNpR7VSnkAELMX0aqZcP=rHs2ddoig@mail.gmail.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>
Subject: Re: About backups
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Length: 2807
Archived-At: <https://www.postgresql.org/message-id/2022327491.4341234.1769452625380%40mail.yahoo.com>
Precedence: bulk

I can't change my expectations. It's either you do it or I won't certify yo=
u, 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 i=
t.

 On Monday, January 26, 2026 at 01:23:05 PM GMT-5, Ron Johnson <ronljohnson=
jr@gmail.com> wrote:

 On Mon, Jan 26, 2026 at 12:52 PM <felix.quintgz@yahoo.com> wrote:I'm havin=
g a problem with this. I'm repurposing an old application written in Visual=
 Basic 6 that did allow backups through signed stored procedures.
You must change your=C2=A0expectations and=C2=A0way of thinking.=C2=A0 Post=
gresql is not SQL Server, and thus cannot be managed=C2=A0the same=C2=A0way=
 as SQL Server.=C2=A0 That is a fact of life which you must accept.=C2=A0Th=
is is a requirement for financial applications; the user can perform a back=
up whenever they want, but they can't access the database.

"ssh to a Linux account dedicated to pgbackrest" within the application is =
my first thought.=C2=A0 Note, though, that pgbackrest does not have BACKUP =
DATABASE's COPY_ONLY feature.=C2=A0 If you need that, pg_dump is your only=
=C2=A0option.
The new application is web-based, deployed in containers, and the database =
server container is not the same as the application's, so I can't use pg_du=
mp in the application, or at least I don't know how to do it.

=C2=A0On Monday, January 26, 2026 at 12:31:48 PM GMT-5, Ron Johnson <ronljo=
hnsonjr@gmail.com> wrote:


On Mon, Jan 26, 2026 at 11:11 AM Adrian Klaver <adrian.klaver@aklaver.com> =
wrote:

On 1/26/26 08:01, felix.quintgz@yahoo.com wrote:

> Is there a way to implement the SQL Server command 'BACKUP DATABASE'?

Not from within the Postgres instance.

You will need to use:

https://www.postgresql.org/docs/current/app-pgdump.html

Felix,=C2=A0pg_dump is a logical export tuned for speed and multithreading.=
=C2=A0 Almost certainly not what you want.

pgbackrest is the equivalent of BACKUP DATABASE and BACKUP LOG.=C2=A0 It's =
an external program (stuffing everything in the database engine is not The =
Unix Way) which typically you run from cron.=C2=A0Redrirect=C2=A0stdout and=
 stderr to a log file with a timestamp in the name.=C2=A0 (That, at least, =
is what I've been doing for 8 years.=C2=A0 It works perfectly.)

pgbackrest also has an "info" option which gives you details of all the bac=
kups currently in the repository.=C2=A0>
> Is there a way to see the restores performed on a database?
> Is there an equivalent table to msdb.dbo.restorehistory in SQL Server?
> Is there a way to implement an equivalent if one doesn't exist?
=C2=A0From what I understand there are various ways of doing this in SQL
Server, which way are you interested in?
--
Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.
<Redacted> lobster!