On 22/04/2004, Guy Fraser <guy(at)incentre(dot)net> wrote To pgsql-general(at)postgresql(dot)org:
> >Shouldn't the Database server be the entity that decides when vacuum is
> 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
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?) :)
Philipp Buehler, aka fips | <double-p>
cvs -d /dev/myself commit -m "it's my life" dont/you/forget
In response to
pgsql-general by date
|Next:||From: John Sidney-Woollett||Date: 2004-04-23 06:32:56|
|Subject: Re: Unicode + LC_COLLATE|
|Previous:||From: Greg Stark||Date: 2004-04-23 04:37:59|
|Subject: Re: staggered query?|