On 4/13/17 17:52, Petr Jelinek wrote: > On 12/04/17 06:10, Peter Eisentraut wrote: >> On 3/24/17 10:49, Petr Jelinek wrote: >>> Rebase after table copy patch got committed. >> >> You could please sent another rebase of this, perhaps with some more >> documentation, as discussed downthread. >> >> Also, I wonder why we don't offer the other values of >> synchronous_commit. In any case, we should keep the values consistent. >> So on should be on and local should be local, but not mixing it. >> > > Now that I am back from vacation I took look at this again. The reason > why I did only boolean initially is that he other values just didn't > seem all that useful. But you are right it's better to be consistent and > there is no real reason why not to allow all of the possible values. > > So how about the attached?
committed -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers