From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
Date: | 2012-12-27 23:02:36 |
Message-ID: | CAFcNs+p-gsnS7wpcvwS4Lsy+Bf8iSv8co0r26V19b57vEybSGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Dec 27, 2012 at 2:04 PM, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
wrote:
>
>
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> >>>> This proposal is about add a column "datcreated" on "pg_database" to
store
> >>>> the "timestamp" of the database creation.
> >
> > I'm inclined to think that anyone who really needs this should be
> > pointed at event triggers. That feature (if it gets in) will allow
> > people to track creation/DDL-change times with exactly the behavior
> > they want.
>
> Agreed.
>
+1
> Maybe the best way to reconciliate both your views would be to provide
> the previous example in the event trigger docs?
>
+1
If all of you agree I can improve the event trigger docs...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2012-12-27 23:09:18 | Re: fix bgworkers in EXEC_BACKEND |
Previous Message | Fabrízio de Royes Mello | 2012-12-27 22:58:36 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |