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

From Michael Nolan
Subject Re: why select count(*) consumes wal logs
Date
Msg-id CAOzAqu+M0-yBqTHcyoH1xd5MhWRCg6xBB58wAROS4HMXYqqg=Q@mail.gmail.com
Whole thread Raw
In response to why select count(*) consumes wal logs  (Ravi Krishna <srkrishna1@aol.com>)
Responses Re: why select count(*) consumes wal logs
List pgsql-general


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.)
--
Mike Nolan

pgsql-general by date:

Previous
From: Ravi Krishna
Date:
Subject: Re: why select count(*) consumes wal logs
Next
From: Ron
Date:
Subject: Re: why select count(*) consumes wal logs