Re: why select count(*) consumes wal logs

Ron <ronljohnsonjr@xxxxxxxxx> · Tue, 6 Nov 2018 11:19:54 -0600



    On 11/06/2018 11:12 AM, Michael Nolan wrote:

    
      On Tue, Nov 6, 2018 at 11:08 AM Ravi Krishna <srkrishna1@xxxxxxx>
        wrote:

        
          PG 10.5

            
            I loaded 133 million rows to a wide table (more than 100
            cols) via COPY. 

          
          It's always a good idea after doing a large scale data
            load to do a vacuum analyze on the table (or the entire
            database.)
          

    I understand the need to ANALYZE (populate the histograms needed by
    the dynamic optimizer), but why VACUUM (which is recommended after
    updates and deletes).

    
    Thanks

    
    -- 

      Angular momentum makes the world go 'round.