| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Subject: | Re: Replication/backup defaults |
| Date: | 2017-01-03 12:34:18 |
| Message-ID: | CAB7nPqRmC7t=wyJO7L8pzQeZ+38_8Owyr1QzZfZ+FbzNHUjQpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 2, 2017 at 10:55 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> In the hope of making things better in 10.0, I remove my objection. If
> people want to use wal_level = minimal they can restart their server
> and they can find that out in the release notes.
>
> Should we set wal_level = replica or wal_level = logical as the
> default for 10.0?
replica sounds like a better default to me as most users use at least
archiving. Logical decoding is still fresh though, and its use is not
that wide. Have there been any study on its performance impact
compared to replica by the way?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-01-03 12:47:37 | Re: gen_random_uuid security not explicit in documentation |
| Previous Message | Rahila Syed | 2017-01-03 12:27:35 | Re: Assignment of valid collation for SET operations on queries with UNKNOWN types. |