Scott Marlowe <smarlowe@xxxxxxxxxxxxxxxxx> writes: > On Fri, 2005-06-03 at 13:40, Alex Turner wrote: >> One might even suggest that this should really be a default for all >> tables everywhere, because at some time or another, someone wants to >> know when something got put in the database... > That kind of designing is what leads to bloated, overweight programs... Agreed --- it is much more important to be sure that we have the features needed to let people add these sorts of behaviors for themselves (in this case, triggers). 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 regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
