| From: | rob stone <floriparob(at)tpg(dot)com(dot)au> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: About backups |
| Date: | 2026-01-27 02:59:58 |
| Message-ID: | 5efd76b75e527a6558dd69ba4364699f256a813a.camel@tpg.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2026-01-26 at 17:44 +0000, felix(dot)quintgz(at)yahoo(dot)com wrote:
>
> Any method that allows me to know who accessed the database and when.
>
> 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.
>
>
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wim Rouquart | 2026-01-27 12:18:20 | RE: Index (primary key) corrupt? |
| Previous Message | Chris Nestrud | 2026-01-26 23:36:29 | Not read: The best way to solve a problem |