Am I right in my thinking that Postgres does not have a pseudo timestamp
field that is updated whenever a row is added or updated?   Did it used
to have one before time travel was removed?

If no timestamp field, are there any other pseudo fields that are
updated every time?  I noticed that the 'ctid' field seems to qualify,
but what does something like (1,54) mean?

Thanks for any help.

Byron


Wed, 10 Jun 1998 13:19:23 -0400
Byron Nikolaidis <byronn@insightdist.com>
Timestamp field
On Wed, 10 Jun 1998, Byron Nikolaidis wrote:

> Am I right in my thinking that Postgres does not have a pseudo timestamp
> field that is updated whenever a row is added or updated?   Did it used
> to have one before time travel was removed?
> 
> If no timestamp field, are there any other pseudo fields that are
> updated every time?  I noticed that the 'ctid' field seems to qualify,
> but what does something like (1,54) mean?
> 
> Thanks for any help.
> 
> Byron

Seems that XMIN field is updated whenever a row is inserted or updated.
see man sql.
                                                            Jose'


Thu, 11 Jun 1998 10:56:07 +0000 (UTC)
"Jose' Soares Da Silva" <sferac@bo.nettuno.it>
Re: [HACKERS] Timestamp field