Re: Fwd: [PERFORM] Vacuum Full + Cluster + Vacuum full = non removable dead rows

2010-08-21 Thread Alexandre de Arruda Paes
2010/8/21 Dimitri > Great! - it's what I expected until now :-) > but discussion in this thread put my mind in trouble :-)) > > So, the advice for Alexandre here is just to check the age of the > oldest running transaction and the last time when the table in > question was modified.. - if modific

Re: Fwd: [PERFORM] Vacuum Full + Cluster + Vacuum full = non removable dead rows

2010-08-21 Thread Dimitri
Great! - it's what I expected until now :-) but discussion in this thread put my mind in trouble :-)) So, the advice for Alexandre here is just to check the age of the oldest running transaction and the last time when the table in question was modified.. - if modification time is older than the ol

Re: Fwd: [PERFORM] Vacuum Full + Cluster + Vacuum full = non removable dead rows

2010-08-21 Thread Scott Marlowe
No, it means it can't clean rows that are younger than the oldest transaction currently in progress. if you started a transaction 5 hours ago, then all the dead tuples created in the last 5 hours are not recoverable. Dead tuples created before that transaction are recoverable. If you run transac

Re: Fwd: [PERFORM] Vacuum Full + Cluster + Vacuum full = non removable dead rows

2010-08-21 Thread Dimitri
So, does it mean that VACUUM will never clean dead rows if you have a non-stop transactional activity in your PG database???... (24/7 OLTP for ex.) Rgds, -Dimitri On 8/19/10, Kevin Grittner wrote: > Alexandre de Arruda Paes wrote: >> 2010/8/18 Tom Lane > >>> There's an open transaction somewh