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. It's like trying to prevent
'rm -rf /*'. And it's not like you can easily set anything in
postgresql.conf by accident.
--
Peter Eisentraut peter_e@gmx.net
