| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Alex Turner <armtuk(at)gmail(dot)com>, Wiebe de Jong <wiebedj(at)shaw(dot)ca>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Determining when a row was inserted |
| Date: | 2005-06-03 23:05:07 |
| Message-ID: | 878y1rdot8.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> As it happens, the original Berkeley-era Postgres did indeed add
> creation and deletion timestamps to every row, as part of their "time
> travel" feature. That got ripped out very soon after the code left
> Berkeley, because the overhead was just unacceptable ... and our
> threshold for unacceptable performance was a whole lot higher then
> than it is today ...
>
> It's worth noting in connection with this Joe Hellerstein's description
> of Berkeley-era Postgres:
> http://archives.postgresql.org/pgsql-hackers/2002-06/msg00085.php
The followups are fascinating too. The next three messages immediately begin
discussing how to get back this feature at least as an option.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2005-06-03 23:23:28 | Re: Autonomous Transactions |
| Previous Message | Matt Miller | 2005-06-03 23:04:29 | Re: Autonomous Transactions |