Search Postgresql Archives

Re: why select count(*) consumes wal logs

Subject: Re: why select count(*) consumes wal logs
From: Ravi Krishna <srkrishna1@xxxxxxx>
Date: Wed, 7 Nov 2018 14:10:22 +0000 (UTC)
Cc: pgsql-general@xxxxxxxxxxxxxxxxxxxx
In-reply-to: <E9FA92C2921F31408041863B74EE4C2001BCB92BDD@CCPMAILDAG03.cantab.local>
References: <653931906.1147337.1541523848244.ref@mail.yahoo.com> <653931906.1147337.1541523848244@mail.yahoo.com> <26567.1541526011@sss.pgh.pa.us> <CAD+GXYOczcCYKk=6cst5Zn5d8Ew_fYnDtf-kyam6y0qmLE60Mw@mail.gmail.com> <E9FA92C2921F31408041863B74EE4C2001BCB90585@CCPMAILDAG03.cantab.local> <1709325689.226793.1541591667311@mail.yahoo.com> <E9FA92C2921F31408041863B74EE4C2001BCB92BDD@CCPMAILDAG03.cantab.local>

> select data_page_checksum_version from pg_control_init()

returned 1.  So we have page_checksum turned on, and wal_log_hints off.

Follow-Ups:
- Re: why select count(*) consumes wal logs
  - From: Thomas Kellerer

References:
- why select count(*) consumes wal logs
  - From: Ravi Krishna
- Re: why select count(*) consumes wal logs
  - From: Tom Lane
- Re: why select count(*) consumes wal logs
  - From: Bruno Lavoie
- RE: why select count(*) consumes wal logs
  - From: Steven Winfield
- Re: why select count(*) consumes wal logs
  - From: Ravi Krishna
- RE: why select count(*) consumes wal logs
  - From: Steven Winfield