Melvin Davidson wrote:
Can anyone tell me why there is no relcreated column in pg_class to track
the creation date of an object?
It seems to me it would make sense to have one as it would facilitate
auditing of when objects are created. In addition, it would also facilitate
the dropping of
Can anyone tell me why there is no relcreated column in pg_class to track
the creation date of an object?
It seems to me it would make sense to have one as it would facilitate
auditing of when objects are created. In addition, it would also facilitate
the dropping of objects that have exceeded a
I thank everyone for their feedback regarding the omission of object
creation date from the catalog.
I do respect the various reasons for not including it, but I feel it is my
duty to draw out this issue a bit longer.
I would like to counter the argument that a restore from a dump will
override
Yep.
Still created once - instantiated repeated times, but created once. Try
federated metadata records only one original creation date which is an
explicit attribute of a record. Last copied, updated, edited are different.
Creation date can be when first entered into a spreadsheet, or
On 05/12/2015 06:33 PM, Melvin Davidson wrote:
I thank everyone for their feedback regarding the omission of object
creation date from the catalog.
I do respect the various reasons for not including it, but I feel it is
my duty to draw out this issue a bit longer.
I would like to counter the
On 05/12/2015 12:51 PM, Melvin Davidson wrote:
Can anyone tell me why there is no relcreated column in pg_class to
track the creation date of an object?
So what date would it track?:
1) The date in the original database?
2) The date the table was restored to another database cluster?
3) The
On 05/12/2015 12:51 PM, Melvin Davidson wrote:
Can anyone tell me why there is no relcreated column in pg_class to
track the creation date of an object?
Meant to add to my previous post, back before I 'discovered' version
control I use to put the creation date in the table COMMENT:
Adrian,
You are over thinking this. An object is only created once! That is what
I meant by relcreatedate. If it is dropped, then it is deleted from the
catalogs. If it is modified, then it does NOT affect the creation date.
Everything else is superfluous.
It is also not unusual for tables to
Melvin Davidson melvin6...@gmail.com writes:
You are over thinking this. An object is only created once!
Yeah? Would you expect that pg_dump followed by pg_restore would preserve
the original creation date? What about pg_upgrade?
This has come up many times before, and we've always decided
On 05/12/2015 03:44 PM, Melvin Davidson wrote:
Adrian,
You are over thinking this. An object is only created once! That is
what I meant by relcreatedate. If it is dropped, then it is deleted from
the catalogs. If it is modified, then it does NOT affect the creation
date. Everything else is
On Tue, May 12, 2015 at 6:33 PM, Melvin Davidson melvin6...@gmail.com
wrote:
I thank everyone for their feedback regarding the omission of object
creation date from the catalog.
I do respect the various reasons for not including it, but I feel it is my
duty to draw out this issue a bit
11 matches
Mail list logo
