Re: Add relcreated (timestamp) column to pg_class catalog to record the time an object was created
От | Adrian Klaver |
---|---|
Тема | Re: Add relcreated (timestamp) column to pg_class catalog to record the time an object was created |
Дата | |
Msg-id | 5718ED00.5010600@aklaver.com обсуждение исходный текст |
Ответ на | Re: Add relcreated (timestamp) column to pg_class catalog to record the time an object was created (Melvin Davidson <melvin6925@gmail.com>) |
Ответы |
Re: Add relcreated (timestamp) column to pg_class catalog
to record the time an object was created
|
Список | pgsql-general |
On 04/21/2016 07:53 AM, Melvin Davidson wrote: > > "Whether that is worthy or not is the point of your request and really > depends on more input." > Correct. And that is what I am looking for. Stating obscure corner cases > does not rule out the need for an enhancement. If it did, there would be > no point in any enhancement. > As of yet, other than this will not work for certain cases, I have not > heard any argument where this would cause harm to the PostgreSQL > database (performance or security concern) > or that this will take any great effort to implement, as I have already > disproved that in a previous update. Making OIDs a default column on user tables was probably not a great effort either. Easy and all user tables got a built in PK, until folks started pushing more data into their database and the OID counter wrapped which had consequences for both user and system tables. Just saying I would want to hear more from the folks that deal with the internals. > > -- > *Melvin Davidson* > I reserve the right to fantasize. Whether or not you > wish to share my fantasy is entirely up to you. -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: