Re: Is there a function to save schema history internally?

From: Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Is there a function to save schema history internally?
Date: 2014-08-30 04:00:56
Message-ID: 1409371256.72679.YahooMailNeo@web193504.mail.sg3.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Adrian,

Thanks for the info.

Thanks and regards,
Patrick

On Saturday, August 30, 2014 5:28 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:

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:

http://www.postgresql.org/message-id/20EE50F73664E744AF948F0106FE6DFA585A790C@SEAMBX01.sea.corp.int.untd.com

>
> Thanks and regards,
> Patrick

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Patrick Dung 2014-08-30 04:38:23 How to make use of partitioned table for faster query?
Previous Message Patrick Krecker 2014-08-29 23:26:13 Re: WAL receive process dies