Re: synchronous_commit and remote_write
От | Robert Haas |
---|---|
Тема | Re: synchronous_commit and remote_write |
Дата | |
Msg-id | CA+TgmoYkWdc_WiZt-V1QOtNGmQANXObgEQJF8rFfyaK09WOeOw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: synchronous_commit and remote_write (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: synchronous_commit and remote_write
|
Список | pgsql-hackers |
On Wed, May 9, 2012 at 10:02 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> Another thing I've been wondering is whether, perhaps, we ought to >> keep synchronous_commit tri-valued: on/local/off, and have a separate >> GUC for synchronous_replication_mode. It's a bit arbitrary that "on" >> happens to mean remote fsync rather than remote write/receive. > > You mean the way it originally was? I would agree. No. The original design for sync rep had synchronous_commit with only TWO values, on and off. I think the design we eventually settled on, with three values, was better, and I'm in favor of keeping it. However, there might be some virtue in separating the knob that controls whether we do sync rep from the knob that controls which kind of sync rep we do. I'm not sure. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: