Project

General

Profile

« Previous | Next » 

Revision 10837

Added by Aaron Marcuse-Kubitza about 11 years ago

fix: web/links/index.htm: PostgreSQL: vacuuming: moved info about autovacuum process being aborted to correct bookmark

View differences:

web/links/index.htm
1353 1353 
"Vacuuming (whether automatic or manual) stops at the oldest transaction id that is still in use." (as opposed to skipping past any active transactions to completed ones)
1354 1354 

  		




  1355
  1355
  
    
"autovacuum will abort if it is not able to obtain a table lock within one second"


  		




  
  1356
  
    
                            <DT><A HREF="http://postgresql.1045698.n5.nabble.com/Lock-problem-with-autovacuum-truncating-heap-td4265539.html" name="http://postgresql.1045698.n5.nabble.com/Lock-problem-with-autovacuum-truncating-heap-td4265539.html" ADD_DATE="1377912054" ICON_URI="http://postgresql.1045698.n5.nabble.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://postgresql.1045698.n5.nabble.com/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL - hackers - Lock problem with autovacuum truncating heap</A><a name="PostgreSQL - hackers - Lock problem with autovacuum truncating heap" href="#PostgreSQL - hackers - Lock problem with autovacuum truncating heap" style="margin-left: 0.5em;">&para;</a>


  		




  
  1357
  
    
<DD>page's description: Lock problem with autovacuum truncating heap. We have run across a problem with autovacuum that occurs when it can truncate off a large amount of empty blocks. It behaves different in version 9.0...


  		




  1356
  1358
  
    

  		




  1357
  1359
  
    
&quot;In 9.0, the autovacuum process will be aborted about 1 second after


  		




  1358
  1360
  
    
another transaction starts waiting for a lock. The result is that even a


  		




  1359
  1361
  
    
simple INSERT will take 1 second.&quot;


  		




  1360
  1362
  
    
this means that autovacuum will never complete if clients keep making INSERTs :(


  		




  1361
  
  
    
                            <DT><A HREF="http://postgresql.1045698.n5.nabble.com/Lock-problem-with-autovacuum-truncating-heap-td4265539.html" name="http://postgresql.1045698.n5.nabble.com/Lock-problem-with-autovacuum-truncating-heap-td4265539.html" ADD_DATE="1377912054" ICON_URI="http://postgresql.1045698.n5.nabble.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://postgresql.1045698.n5.nabble.com/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL - hackers - Lock problem with autovacuum truncating heap</A><a name="PostgreSQL - hackers - Lock problem with autovacuum truncating heap" href="#PostgreSQL - hackers - Lock problem with autovacuum truncating heap" style="margin-left: 0.5em;">&para;</a>


  		




  1362
  
  
    
<DD>page's description: Lock problem with autovacuum truncating heap. We have run across a problem with autovacuum that occurs when it can truncate off a large amount of empty blocks. It behaves different in version 9.0...


  		




  1363
  1363
  
    
                        </DL><p>


  		




  1364
  1364
  
    
                        <DT><A HREF="http://journal.tianhao.info/2010/12/postgresql-change-default-encoding-of-new-databases-to-utf-8-optional/" name="http://journal.tianhao.info/2010/12/postgresql-change-default-encoding-of-new-databases-to-utf-8-optional/" ADD_DATE="1335054607" ICON_URI="http://blog.tianhao.info/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://blog.tianhao.info/favicon.ico" style="margin-right: 0.5em;"/>» PostgreSQL – Change Default Encoding of New Databases To UTF-8 (Optional) Journal</A><a name="» PostgreSQL – Change Default Encoding of New Databases To UTF-8 (Optional) Journal" href="#» PostgreSQL – Change Default Encoding of New Databases To UTF-8 (Optional) Journal" style="margin-left: 0.5em;">&para;</a>


  		




  1365
  1365
  
    
                        <DT><A HREF="https://groups.google.com/forum/?fromgroups#!topic/pgsql.general/aitDYC6jMEI" name="https://groups.google.com/forum/?fromgroups#!topic/pgsql.general/aitDYC6jMEI" ADD_DATE="1340396170" ICON_URI="https://groups.google.com/forum/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="https://groups.google.com/forum/favicon.ico" style="margin-right: 0.5em;"/>[GENERAL] ROLLBACK in a function - Google Groups</A><a name="[GENERAL] ROLLBACK in a function - Google Groups" href="#[GENERAL] ROLLBACK in a function - Google Groups" style="margin-left: 0.5em;">&para;</a>


  		












Also available in:  Unified diff