Re: why select count(*) consumes wal logs

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: why select count(*) consumes wal logs
Date: 2018-11-06 17:19:54
Message-ID: 4e7dda1e-b37c-32eb-4605-721473154082@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/06/2018 11:12 AM, Michael Nolan wrote:
> On Tue, Nov 6, 2018 at 11:08 AM Ravi Krishna <srkrishna1(at)aol(dot)com
> <mailto:srkrishna1(at)aol(dot)com>> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kumar, Virendra 2018-11-06 17:38:38 RE: why select count(*) consumes wal logs
Previous Message Michael Nolan 2018-11-06 17:12:01 Re: why select count(*) consumes wal logs