Re: why select count(*) consumes wal logs

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: srkrishna1(at)aol(dot)com
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: why select count(*) consumes wal logs
Date: 2018-11-06 17:12:01
Message-ID: CAOzAqu+M0-yBqTHcyoH1xd5MhWRCg6xBB58wAROS4HMXYqqg=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Nov 6, 2018 at 11:08 AM Ravi Krishna <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.)
--
Mike Nolan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2018-11-06 17:19:54 Re: why select count(*) consumes wal logs
Previous Message Ravi Krishna 2018-11-06 17:05:43 Re: why select count(*) consumes wal logs