Changes between Version 13 and Version 14 of FAQ

Show
Ignore:
Timestamp:
03/13/06 19:15:04 (14 years ago)
Author:
anonymous
Comment:

more typo fixes

Legend:

Unmodified
Added
Removed
Modified

  • FAQ

    v13 v14  
    129129  A: You have to: 
    130130 
    131  1. Run VACUUM ANALYSE often from a script (it's a very cheap, non locking operation, and considering wifidog's very write heavy SQL mix, runing it every hour isn't excessive). 
     131 1. Run VACUUM ANALYZE often from a script (it's a very cheap, non-locking operation, and considering wifidog's very write-heavy SQL mix, running it every hour isn't excessive). 
    132132 1. Make sure the above script works. 
    133  1. If you see you auth server getting progressively slower, run  VACUUM FULL ANALYSE once, and GO TO STEP 2. 
     133 1. If you see your auth server getting progressively slower, run VACUUM FULL ANALYZE once, and GO TO STEP 2. 
    134134 
    135  Explanation:  If you run VACUUM ANALYSE regularily (every night or every hour) you shouldn't need VACUUM FULL ANALYSE. However, if you haven't run VACUUM ANALYSE for a long time, you have to run VACUUM FULL ANALYZE once.  
     135 Explanation:  If you run VACUUM ANALYZE regularily (every night or every hour) you shouldn't need VACUUM FULL ANALYZE. However, if you haven't run VACUUM ANALYZE for a long time, you have to run VACUUM FULL ANALYZE once. 
    136136 
    137  What happens is that without VACUUMing the connection and node tables grows and grows (because they are written to frequently, and postgres being a true ACID database, keep past versions of tuples to insure read consistency).  Simply vacuuming doesn't reclaim the space used by old tuples, it just makes them available for reuse.  If you haven't run VACUUM in a long time, you probably have millions of free tuples that you would, never, ever  
    138 use up in a single day.  VACUUM FULL ANALYZE fixes that. 
     137 What happens is that without VACUUMing the connection and node tables grows and grows (because they are written to frequently, and postgres being a true ACID database, keep past versions of tuples to insure read consistency).  Simply vacuuming doesn't reclaim the space used by old tuples, it just makes them available for reuse.  If you haven't run VACUUM in a long time, you probably have millions of free tuples that you would, never, ever use up in a single day.  VACUUM FULL ANALYZE fixes that. 
    139138 
    140139== Q: There are error messages displayed on the portal pages ==