Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Andrew Sullivan expressed concern about this, too. The thing could
>> be made a little more failsafe if we made it impossible to set
>> ZERO_DAMAGED_PAGES to true in postgresql.conf, or by any means other
>> than an actual SET command --- whose impact would then be limited to
>> the current session. This is kind of an ugly wart on the GUC mechanism,
>> but I think not difficult to do with an assign_hook (it just has to
>> refuse non-interactive settings).
> Fighting against people who randomly change settings without being
> informed about what they do is pointless.
If you don't want an active defense, how about a passive one --- like
just not listing zero_damaged_pages in postgresql.conf.sample? We
already have several variables deliberately not listed there ...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
