From: | Philipp Buehler <pb-pgsql-g(at)mlsub(dot)buehler(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 7.3.4 on Linux: UPDATE .. foo=foo+1 degrades massivly |
Date: | 2004-04-26 19:04:28 |
Message-ID: | 20040426190428.GA21592@srv9.de.buehler.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 26/04/2004, Guy Fraser <guy(at)incentre(dot)net> wrote To Philipp Buehler:
> What if your not the only person accessing the database and someone else
> has an active transaction that was initiated before your transaction was
> committed?
There are row locks for a reason, too?
OTOH that's somewhat like handling a filesystem. if you have
a refcount=x. Just decrease the refcount for completed
transaction and after it this count drops to 0 the tuple can be purged.
> supported, but hopefully it will be configurable to allow 'time travel'
> when required, and allow for a reasonable time to be able to roll back
> transactions.
Hm well. a comitted transaction is one, right? I dont get your
time travel here now.. hmm.
Ciao
--
Philipp Buehler, aka fips | <double-p>
cvs -d /dev/myself commit -m "it's my life" dont/you/forget
From | Date | Subject | |
---|---|---|---|
Next Message | Timothy Perrigo | 2004-04-26 19:12:14 | questions on rules |
Previous Message | Guy Fraser | 2004-04-26 18:53:09 | Re: 7.3.4 on Linux: UPDATE .. foo=foo+1 degrades massivly |