Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
Date
Msg-id CAFcNs+o3t-1fvBvhKTTUY1Twp==i5YTH2KqLexvWYZKY+8oaTQ@mail.gmail.com
Whole thread
In response to Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
List pgsql-hackers

* Stephen Frost <sfrost@snowman.net> wrote:
>
> * Fabrízio de Royes Mello (fabriziomello@gmail.com) wrote:
> > * also we discuss about create two new catalogs, one local and another
> > shared (like pg_description and pg_shdescription) to track creation times
> > of all database objects.
>
> Creating a separate catalog (or two) every time we want to track XYZ for
> all objects is rather overkill...  Thinking about this a bit more, and
> noting that pg_description/shdescription more-or-less already exist as a
> framework for tracking 'something' for 'all catalog entries'- why don't
> we just add these columns to those tables..?  

But those tables are filled only when we execute COMMENT ON statement... then your idea is create a 'null' comment every time we create a single object... is it?

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

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: enhanced error fields
Next
From: Pavel Stehule
Date:
Subject: Re: enhanced error fields