From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Add relcreated (timestamp) column to pg_class catalog to record the time an object was created |
Date: | 2016-04-21 13:09:29 |
Message-ID: | CANu8Fiw2e8-26Us=G6YLX_0BP14APpnbKniXuhuM8iBvHxb+xQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Speaking blindly here but given that we now have event triggers I'm even
more inclined to simply tell people to setup user-space tables and event
triggers to do whatever they want. Is there any reason that combination
cannot solve the problems being brought up? I get the desirability of
having something in-core but this seems like a perfect problem for which
PGXN should be the solution."
Wekk, yes and no. To use event triggers requires that a user first create
their own audit table, then create a function to process the event, and
finally create the event trigger. That works fine for the single database
situation, but when you have hundreds of servers and databases to monitor
(as I did), it makes the implementation a bit more daunting. Whereas having
relcreatedat would mean "no muss, no fuss". :)
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2016-04-21 13:40:18 | Re: Add relcreated (timestamp) column to pg_class catalog to record the time an object was created |
Previous Message | Alex Ignatov | 2016-04-21 13:00:50 | Re: Initdb --data-checksums by default |