Re: why select count(*) consumes wal logs - Mailing list pgsql-general

From Ron
Subject Re: why select count(*) consumes wal logs
Date
Msg-id 4e7dda1e-b37c-32eb-4605-721473154082@gmail.com
Whole thread Raw
In response to Re: why select count(*) consumes wal logs  (Michael Nolan <htfoot@gmail.com>)
Responses RE: why select count(*) consumes wal logs
List pgsql-general
On 11/06/2018 11:12 AM, Michael Nolan wrote:
On Tue, Nov 6, 2018 at 11:08 AM Ravi Krishna <srkrishna1@aol.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.

pgsql-general by date:

Previous
From: Michael Nolan
Date:
Subject: Re: why select count(*) consumes wal logs
Next
From: "Kumar, Virendra"
Date:
Subject: RE: why select count(*) consumes wal logs