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

From Craig Ringer
Subject Re: Disable WAL completely - Performance and Persistency research
Date
Msg-id CAMsr+YEeGZCT24hd3HeDZkPC8BAhX3s1GqtUUYDzC+seqCS3Dg@mail.gmail.com
Whole thread Raw
In response to Re: 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 10 July 2016 at 18:27, Netanel Katzburg <netanel10k@gmail.com> wrote:
 

BUT, both options are not good, as they are stopping me from even running initdb. 



The easiest path for testing will be to use an unpatched PostgreSQL to `initdb` and create a new database. Then start up a patched one that simply skips WAL writing against an already-`initdb`'d data directory.

You probably won't be able to safely restart PostgreSQL, but all you're doing is performance analsys so one-shot operation on a throw-away data directory is probably fine. 
 

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: PSA: Systemd will kill PostgreSQL
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench - minor doc improvements