| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, "PostgreSQL Hackers ML" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Keeping creation time of objects |
| Date: | 2008-09-09 19:55:12 |
| Message-ID: | 603c8f070809091255i73b6d040j609c24d12d8347b3@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> There isn't sufficient support for such a "feature".
It sounds like a useful feature to me.
> In any case, why
> would creation time (as opposed to any other time, eg last schema
> modification, last data modification, yadda yadda) be especially
> significant?
Those would be nice to have too, but last data modification is
doubtless too expensive to compute and keep up to date.
> Would you expect it to be preserved over dump/restore?
Definitely not. Then it wouldn't really be the creation time, would it?
> How about every other object type in the system?
Good idea. I wouldn't bother for things that are intended to be
ephemeral, but having this for, say, functions, would be nice.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2008-09-09 20:03:56 | Re: Keeping creation time of objects |
| Previous Message | Devrim GÜNDÜZ | 2008-09-09 19:46:04 | Re: Keeping creation time of objects |