Message-ID: <5efd76b75e527a6558dd69ba4364699f256a813a.camel@tpg.com.au>
Subject: Re: About backups
From: rob stone <floriparob@tpg.com.au>
To: pgsql-general@lists.postgresql.org
Date: Tue, 27 Jan 2026 13:59:58 +1100
In-Reply-To: <2097370962.4296686.1769449473672@mail.yahoo.com>
References: <1730736265.4259921.1769443263077.ref@mail.yahoo.com>
		 <1730736265.4259921.1769443263077@mail.yahoo.com>
		 <f88a803f-2954-44c5-bd29-e7f1dc5f9d02@aklaver.com>
	 <2097370962.4296686.1769449473672@mail.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2-8 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/5efd76b75e527a6558dd69ba4364699f256a813a.camel%40tpg.com.au>
Precedence: bulk

On Mon, 2026-01-26 at 17:44 +0000, felix.quintgz@yahoo.com wrote:
>=20
> Any method that allows me to know who accessed the database and when.
>=20
> This is necessary for auditing the database. It's a requirement for
> financial applications.
> I can't use a table within the database because it gets overwritten
> upon restoration.
>=20
>=20

A user has access to the application and logs on. You record that in a
table of successful log-ons. You also need a table of unsuccessful log-
on attempts. E.g, mis-typed password, access window expired, etc.

None of that data is lost when a database restore occurs.
You haven't said if you intend doing hot backups or cold backups.

Have you read Chapter 25 of the documentation?


>I don't have admin access to the database server; in SQL Server, I
>resolved this using signed stored procedures.


Most IT departments have a person known as the DBA. They are involved
in the design of the database to fit the application and after it goes
live are usually responsible for checking the back-ups.
You haven't stated what your role is with the development of this
application.


Rob