On 22/04/2004, Guy Fraser <guy@incentre.net> wrote To pgsql-general@postgresql.org: > >Shouldn't the Database server be the entity that decides when vacuum is > >needed? > > How is the database supposed to know when you want to purge records? > Once a vacuum has been run, the table can not be rolled back or time > traveled. Hmm, if the UPDATE is in a transaction block. After this block is committed, the deleted tuple could be purged if there is a flag. Like, either in the schema 'purge-on-commit', or as an option like 'UPDATE PURGE'? Just an idea.. (Brainfart?) :) ciao -- Philipp Buehler, aka fips | <double-p> cvs -d /dev/myself commit -m "it's my life" dont/you/forget ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
