| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christian Ullrich <chris(at)chrullrich(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Initial release notes created for 9.6 |
| Date: | 2016-05-06 21:20:42 |
| Message-ID: | 12878.1462569642@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christian Ullrich <chris(at)chrullrich(dot)net> writes:
> * Tom Lane wrote:
>> To my mind, an option that's set to 1 is "enabled". Should the second
>> para read "Do not disable ..."? Or maybe we should reverse the sense
>> of the flag, so that the default state can be 0 == disabled?
> Well spotted, thanks. It should be "disable" instead.
> This is left from when the sense of the option _was_ the other way
> around (it was called "real_realm" then). I reversed and renamed it
> after Magnus reviewed the patch and was -- correctly -- opposed to the name.
Oh, OK, I don't wish to re-open the issue if it's already been thought
about. Will just s/enable/disable/ instead.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2016-05-06 21:28:17 | Re: Feature request: make cluster_name GUC useful for psql prompts |
| Previous Message | Andres Freund | 2016-05-06 21:20:16 | Re: Reviewing freeze map code |