Re: why select count(*) consumes wal logs

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: srkrishna1(at)aol(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: why select count(*) consumes wal logs
Date: 2018-11-06 18:27:02
Message-ID: CAOzAquLTB7KVYod965fPkA3Mn1K5r7=Cp8RTyEiXjAzs2cq6Tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Nov 6, 2018 at 11:40 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>
> That represents setting the yes-this-row-is-committed hint bits on the
> newly loaded rows. The first access to any such row will set that bit,
> whether it's a select or a VACUUM or whatever.
>
> Tom, does that include ANALYZE?
--
Mike Nolan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ondřej Bouda 2018-11-06 18:31:50 Re: backend crash on DELETE, reproducible locally
Previous Message Igor Korot 2018-11-06 18:06:14 Re: Fwd: Log file