| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | "Edson F(dot) Lidorio" <edson(at)openmailbox(dot)org>, Melvin Davidson <melvin6925(at)gmail(dot)com>, Zlatko Asenov <zlatko(dot)asenov(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Get the date of creation of objects in the database |
| Date: | 2016-02-23 00:19:05 |
| Message-ID: | 56CBA579.6040502@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 02/22/2016 03:24 PM, Edson F. Lidorio wrote:
>
>
> + 1
>
> Listen11similar discussionat [1]
>
> [1]
> http://pgsql-hackers.postgresql.narkive.com/TQSHWw1l/proposal-store-timestamptz-of-database-creation-on-pg-database
Where the above leads to is implementing a version control system inside
the database. Not necessarily a bad idea, but something I personally see
as better handled by dedicated version control software. Myself, I use
sqitch(http://sqitch.org/) in combination with Mercurial to keep track
of object creation and changes. Being independent of the database it
handles dealing with multiple instances(think dev, testing, production)
easier.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-02-23 02:09:13 | Re: synch streaming replication question |
| Previous Message | Edson F. Lidorio | 2016-02-22 23:24:26 | Re: Get the date of creation of objects in the database |