| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: About backups |
| Date: | 2026-01-26 19:23:07 |
| Message-ID: | CANzqJaCcoT+SpR4rb7bt=fsDKEetD0Z2pBZCay4+Eq1EMuY-sw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jan 26, 2026 at 1:42 PM 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."
But it is! That's exactly how you -- and IIRC *the only* way to -- backup
SQL Server databases (typically from Agent, which is like pg_cron but much
more featureful, and completely integrated into SSMS and SQL Server).
Every CLI or GUI method of doing a backup calls BACKUP DATABASE and/or
BACKUP LOG behind the scenes.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | felix.quintgz | 2026-01-26 19:24:45 | Re: About backups |
| Previous Message | Christophe Pettus | 2026-01-26 18:42:37 | Re: About backups |