Re: Disable WAL completely - Performance and Persistency research - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Disable WAL completely - Performance and Persistency research
Date
Msg-id CAB7nPqSgiuedKG8fqKC=e6eNQp5ssVyAGZ9SRbGFj=BSVCmaDA@mail.gmail.com
Whole thread Raw
In response to Disable WAL completely - Performance and Persistency research  (Netanel Katzburg <netanel10k@gmail.com>)
Responses Re: Disable WAL completely - Performance and Persistency research  (Netanel Katzburg <netanel10k@gmail.com>)
List pgsql-hackers
On Thu, Jul 7, 2016 at 5:01 PM, Netanel Katzburg <netanel10k@gmail.com> wrote:
> 1. Disable the WAL by not writing anything to the xlog directory. I don't
> care about recovery/fault tolerance or PITR/ replication etc at the moment.
> I'm aware that the WAL and checkpoint are bind in many ways and are crucial
> for PG core features.
> Any guidance on how to do so would be appreciated :)

WAL insertion routines are in xloginsert.c. Did you try to play with those?
-- 
Michael



pgsql-hackers by date:

Previous
From: Netanel Katzburg
Date:
Subject: Disable WAL completely - Performance and Persistency research
Next
From: Tom Lane
Date:
Subject: Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information.