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

From Steven Winfield
Subject RE: why select count(*) consumes wal logs
Date
Msg-id E9FA92C2921F31408041863B74EE4C2001BCB90585@CCPMAILDAG03.cantab.local
Whole thread Raw
In response to Re: why select count(*) consumes wal logs  (Bruno Lavoie <bl@brunol.com>)
Responses Re: why select count(*) consumes wal logs
List pgsql-general

As long as you don’t have page checksums turned on, you can prevent this by turning off wal_log_hints.

 

Steve.





This email is confidential. If you are not the intended recipient, please advise us immediately and delete this message. The registered name of Cantab- part of GAM Systematic is Cantab Capital Partners LLP. See - http://www.gam.com/en/Legal/Email+disclosures+EU for further information on confidentiality, the risks of non-secure electronic communication, and certain disclosures which we are required to make in accordance with applicable legislation and regulations. If you cannot access this link, please notify us by reply message and we will send the contents to you.

GAM Holding AG and its subsidiaries (Cantab – GAM Systematic) will collect and use information about you in the course of your interactions with us. Full details about the data types we collect and what we use this for and your related rights is set out in our online privacy policy at https://www.gam.com/en/legal/privacy-policy. Please familiarise yourself with this policy and check it from time to time for updates as it supplements this notice

pgsql-general by date:

Previous
From: Tony Shelver
Date:
Subject: Re: Question about index on different tablespace and rebuild it
Next
From: "范孝剑(康贤)"
Date:
Subject: Can I skip function ResolveRecoveryConflictWithSnapshot if setting hot_standby_feedback=on all the time