| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Netanel Katzburg <netanel10k(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Disable WAL completely - Performance and Persistency research |
| Date: | 2016-07-11 05:27:52 |
| Message-ID: | CAMsr+YEeGZCT24hd3HeDZkPC8BAhX3s1GqtUUYDzC+seqCS3Dg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10 July 2016 at 18:27, Netanel Katzburg <netanel10k(at)gmail(dot)com> wrote:
> BUT, both options are not good, as they are stopping me from even running i
> *nitdb.*
>
>
>
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2016-07-11 05:30:14 | Re: pgbench - minor doc improvements |
| Previous Message | Craig Ringer | 2016-07-11 05:25:51 | Re: PSA: Systemd will kill PostgreSQL |