| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk>, Pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Is there a function to save schema history internally? |
| Date: | 2014-08-29 21:27:36 |
| Message-ID: | 5400F048.1020106@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/29/2014 11:23 AM, Patrick Dung wrote:
> Hello Postgresql users,
>
> Is there a function to save schema history internally?
> By keeping the schema history inside the DB, we can keep track of what
> and when is changed in the schema.
>
> While searching google. It seems it is a limitation with the audit trigger:
> https://wiki.postgresql.org/wiki/Audit_trigger#Limitation:_Cannot_audit_DDL
Well going forward, 9.4+, there are EVENT TRIGGERS
http://www.postgresql.org/docs/9.4/static/event-triggers.html
For a recent thread on what is possible or not see:
>
> Thanks and regards,
> Patrick
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emi Lu | 2014-08-29 21:29:30 | Re: alter column to varchar without view drop/re-creation |
| Previous Message | Andres Freund | 2014-08-29 21:11:25 | Re: WAL receive process dies |