Skip site navigation (1) Skip section navigation (2)

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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>,Christopher Browne <cbbrowne(at)gmail(dot)com>,Hannu Krosing <hannu(at)2ndquadrant(dot)com>,Andres Freund <andres(at)2ndquadrant(dot)com>,Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>,Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
Date: 2013-01-05 19:31:53
Message-ID: 20130105193152.GV16126@tamriel.snowman.net (view raw or flat)
Thread:
Lists: pgsql-hackers
* Fabrízio de Royes Mello (fabriziomello(at)gmail(dot)com) wrote:
> 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?

Yes, and have the actual 'description' field (as it's variable) at the
end of the catalog.

Regarding the semantics of it- I was thinking about how directories and
unix files work.  Basically, adding or removing a sub-object would
update the alter time on the object itself, changing an already existing
object or sub-object would update only the object/sub-object's alter
time.  Creating an object or sub/object would set its create time and
alter time to the same value.  I would distinguish 'create' from
'ctime', however, and have our 'create' time be only the actual
*creation* time of the object.  ALTER table OWNER TO user; would update
"table"s alter time.

Open to other thoughts on this and perhaps we should create a wiki page
to start documentating the semantics.  Once we get agreement there, it's
just a bit of code. :)

	Thanks,

		Stephen

In response to

Responses

pgsql-hackers by date

Next:From: Joshua BerkusDate: 2013-01-05 20:50:05
Subject: Re: Cascading replication: should we detect/prevent cycles?
Previous:From: Tom LaneDate: 2013-01-05 19:15:30
Subject: Re: Re: [COMMITTERS] pgsql: Invent a "one-shot" variant of CachedPlans for better performanc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group