| From: | Vipin Madhusoodanan <vipin(dot)madhusoodanan(at)gmail(dot)com> |
|---|---|
| To: | Rui DeSousa <rui(at)crazybean(dot)net> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Query on User account password change details |
| Date: | 2021-05-09 03:46:00 |
| Message-ID: | CAPOO3u5Nqn+16PS5=9HNJ3AbG42-GDEWp+xy=UMOnQehudr48A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thanks much Rui and All for the valuable inputs. Rui's suggested solution
would be sufficient for our audit requirement.
Thank you,
Vipin
On Sat, May 8, 2021, 7:59 PM Rui DeSousa <rui(at)crazybean(dot)net> wrote:
>
>
> > On May 8, 2021, at 8:55 PM, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> >
> > The problem with this scheme is that any role with SUPERUSER privs can
> modify that table.
> >
>
> True; and if that is a concern then audit the table from a different
> system where those superusers do not have access to.
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Scalia | 2021-05-09 23:18:38 | Technical guidance for a large partition table |
| Previous Message | Rui DeSousa | 2021-05-09 00:58:52 | Re: Query on User account password change details |