agora inbox for postgres@postgres.berkeley.edu
help / color / mirror / Atom feedtime travel
3+ messages / 3 participants
[nested] [flat]
* time travel
@ 1994-04-29 04:57 Wolfgang Effenberg <wolf@ironbark.ucnv.edu.au>
0 siblings, 0 replies; 3+ messages in thread
From: Wolfgang Effenberg @ 1994-04-29 04:57 UTC (permalink / raw)
To: legacy
Hi,
I am interested to hear from anyone who has utilised the ability of postgres
for holding historical information especially for larger databases and or
database with a high transaction rate.
Has postgres been used as the attribute database for any graphics package. I
am thinking here of the possibility of using postgres in a GIS application?
Any comments or infoemation most welcome.
regards
Wolfgang Effenberg email wolf@ironbark.ucnv.deu.au
===============================================================================
To add/remove yourself from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
===============================================================================
^ permalink raw reply [nested|flat] 3+ messages in thread
* time travel
@ 1994-11-09 13:57 Giles Nelson <Giles.Nelson@cl.cam.ac.uk>
0 siblings, 1 reply; 3+ messages in thread
From: Giles Nelson @ 1994-11-09 13:57 UTC (permalink / raw)
To: legacy
Hello all.
I have a query about the facilities POSTGRES gives for historical databases,
what the user manual terms as `time travel'.
Classes can be created to be archival or not. The default is not. Therefore
after instances are deleted, purged and the database vacuumed those instances
will have been physically deleted.
Alternatively a class may be defined as archival. Even after vacuuming
therefore deleted instances are still accessible.
The time stamp that POSTGRES appears to attach to each instance is what is
often termed `database time', that is the time at which the instance was
actually inserted into the database.
I would like to use the built-in facilities that POSTGRES has for time travel
but I wish to time stamp each instance with an `event time', that is the time
which is associated with the instance itself, such as a birth date.
My impression is that this is not possible and I will have to use a time
attribute within a relation. However I wondered if anyone else had experience
of doing directly and therefore retaining the use of built-in facilities.
Giles Nelson.
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: time travel
@ 1994-11-09 18:50 Paul M. Aoki <aoki@cs.berkeley.edu>
parent: Giles Nelson <Giles.Nelson@cl.cam.ac.uk>
0 siblings, 0 replies; 3+ messages in thread
From: Paul M. Aoki @ 1994-11-09 18:50 UTC (permalink / raw)
To: Giles Nelson <Giles.Nelson@cl.cam.ac.uk>; +Cc: legacy
Giles Nelson <Giles.Nelson@cl.cam.ac.uk> writes:
> I would like to use the built-in facilities that POSTGRES has for
> time travel but I wish to time stamp each instance with an `event
> time', that is the time which is associated with the instance
> itself, such as a birth date.
>
> My impression is that this is not possible and I will have to use a
> time attribute within a relation.
correct, the built-in time-travel syntax only works for transaction
commit time, and you cannot change the commit timestamp. the time
*types* are general but the syntax is not.
--
Paul M. Aoki | University of California at Berkeley
aoki@CS.Berkeley.EDU | Dept. of EECS, Computer Science Division (#1776)
| Berkeley, CA 94720-1776
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~1994-11-09 18:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1994-04-29 04:57 time travel Wolfgang Effenberg <wolf@ironbark.ucnv.edu.au>
1994-11-09 13:57 time travel Giles Nelson <Giles.Nelson@cl.cam.ac.uk>
1994-11-09 18:50 ` Paul M. Aoki <aoki@cs.berkeley.edu>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox