Re: Disable WAL completely - Performance and Persistency research

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Netanel Katzburg <netanel10k(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Disable WAL completely - Performance and Persistency research
Date: 2016-07-07 13:17:15
Message-ID: CAB7nPqSgiuedKG8fqKC=e6eNQp5ssVyAGZ9SRbGFj=BSVCmaDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 7, 2016 at 5:01 PM, Netanel Katzburg <netanel10k(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-07-07 14:07:24 Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information.
Previous Message Amit Kapila 2016-07-07 11:27:03 Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information.