Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"

<div dir="ltr"><br />* Stephen Frost <<a href="mailto:sfrost@snowman.net">sfrost@snowman.net</a>> wrote:<br
/>><br/>> Yes, and have the actual 'description' field (as it's variable) at the<br />> end of the catalog.<br
/>><br />> Regarding the semantics of it- I was thinking about how directories and<br />> unix files work.
 Basically,adding or removing a sub-object would<br />> update the alter time on the object itself, changing an
alreadyexisting<br /> > object or sub-object would update only the object/sub-object's alter<br />> time.
 Creatingan object or sub/object would set its create time and<br />> alter time to the same value.  I would
distinguish'create' from<br /> > 'ctime', however, and have our 'create' time be only the actual<br />>
*creation*time of the object.  ALTER table OWNER TO user; would update<br />> "table"s alter time.<br />><br
/><br/>Understood... a "COMMENT" is a database object, then if we add a creation time column to
pg_description/shdescriptiontables how we track his creation time?<br /><br /> <br />><br />> Open to other
thoughtson this and perhaps we should create a wiki page<br />> to start documentating the semantics.  Once we get
agreementthere, it's<br />> just a bit of code. :)<br />><br /><br />+1<br /><br />Regards,<br /><br />--<br
/>Fabríziode Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>> Blog sobre TI: <a
href="http://fabriziomello.blogspot.com">http://fabriziomello.blogspot.com</a><br/>>> Perfil Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/> >> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/></div>