Hi,
On 2025-01-21 13:28:43 -0500, Chapman Flack wrote:
> On 01/19/25 12:02, Tom Lane wrote:
> > You can build that yourself, typically by adding a trigger that stores
> > the value of "current_user" into inserted/updated rows. (If you want
> > to also track deletions, a separate audit log table w
Chapman Flack writes:
> I wonder how close one could get to the customer request (better
> forensics without having to build extra columns and triggers at the
> SQL level) with an extension and existing hooks.
An extension would be a great solution if we can make it work.
> I haven't used it, bu
On 01/19/25 12:02, Tom Lane wrote:
> You can build that yourself, typically by adding a trigger that stores
> the value of "current_user" into inserted/updated rows. (If you want
> to also track deletions, a separate audit log table would work
> better.) The event-trigger feature might also be us
gresql.org ;
Mahesh Rao ; Nazia Zaidi ;
Jitesh Tiwari ; Nick Wagner ;
Scott Corbin ; Mack Bell ;
Avinash Dubey
Subject: [External] : Re: New feature request for adding session information to
PostgreSQL transaction log
Sumanth Vishwaraj writes:
> We would like PostgreSQL to store the details of
On Wed, 15 Jan 2025 08:54:06 +
Sumanth Vishwaraj wrote:
> Oracle Audit Vault and Database Firewall (AVDF) audits/monitors
> database activities. This product helps enterprises to manage the
> security posture of Oracle , PostgreSQL and other databases.
>
> Oracle AVDF helps customers in Indi
Sumanth Vishwaraj writes:
> We would like PostgreSQL to store the details of who made the change
> (user/session) information in the transaction log.
You can build that yourself, typically by adding a trigger that stores
the value of "current_user" into inserted/updated rows. (If you want
to al
To: Sumanth Vishwaraj ;
pgsql-hackers@lists.postgresql.org
Cc: Mahesh Rao ; Nazia Zaidi
; Jitesh Tiwari ; Nick
Wagner ; Mack Bell ; Avinash
Dubey
Subject: RE: New feature request for adding session information to PostgreSQL
transaction log
Sumanth,
We generally add whatever contextual in
On 2020-05-26 12:10, Bert Scalzo wrote:
So far QIKR shows about a
2.5X improvement over the PostgreSQL optimizer when fed bad SQL. I am
not saying the PotsgrSQL optimizer does a poor job, but rather that
QIKR was designed for "garbage in, not garbage out" - so QIKR fixes all
the stupid mistake
I greatly appreciate all the replies. Thanks. I also fully understand and
appreciate all the points made - especially that this idea may not have
general value or acceptance as worthwhile. No argument from me. Let me
explain why I am looking to do this to see if that changes any opinions. I
have wr
On 26.05.2020 04:47, Tomas Vondra wrote:
On Mon, May 25, 2020 at 09:21:26PM -0400, Bruce Momjian wrote:
On Mon, May 25, 2020 at 07:53:40PM -0500, Bert Scalzo wrote:
I am reposting this from a few months back (see below). I am not
trying to be a
pest, just very motivated. I really think this
Michael Paquier writes:
> On Mon, May 25, 2020 at 09:21:26PM -0400, Bruce Momjian wrote:
>> I think your best bet is to try getting someone to write a hook
>> that will do the replacement so that you don't need to modify too much
>> of the Postgres core code. You will need to have the hook update
On Mon, May 25, 2020 at 09:21:26PM -0400, Bruce Momjian wrote:
On Mon, May 25, 2020 at 07:53:40PM -0500, Bert Scalzo wrote:
I am reposting this from a few months back (see below). I am not trying to be a
pest, just very motivated. I really think this feature has merit, and if not
generally worth
On Mon, May 25, 2020 at 09:21:26PM -0400, Bruce Momjian wrote:
> I think your best bet is to try getting someone to write a hook
> that will do the replacement so that you don't need to modify too much
> of the Postgres core code. You will need to have the hook updated for
> new versions of Postgr
On Mon, May 25, 2020 at 07:53:40PM -0500, Bert Scalzo wrote:
> I am reposting this from a few months back (see below). I am not trying to be
> a
> pest, just very motivated. I really think this feature has merit, and if not
> generally worthwhile, I'd be willing to pay someone to code it for me as
14 matches
Mail list logo
