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 CAOzAquLTB7KVYod965fPkA3Mn1K5r7=Cp8RTyEiXjAzs2cq6Tg@mail.gmail.com
Whole thread Raw
In response to Re: why select count(*) consumes wal logs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: why select count(*) consumes wal logs
List pgsql-general



On Tue, Nov 6, 2018 at 11:40 AM Tom Lane <tgl@sss.pgh.pa.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

pgsql-general by date:

Previous
From: Igor Korot
Date:
Subject: Re: Fwd: Log file
Next
From: "Ondřej Bouda"
Date:
Subject: Re: backend crash on DELETE, reproducible locally